What are the ways of interchanging string data between clients and a server in Delphi?

Question

I have a server and some clients (about 50) in an intranet. The clients send short (about 40 character) string data to the server and the server answers with a similar string. There are up to (but not permanently) 2-3 requests per second for each client. The server has to serialize the requests to get the response strings.

The system should have as less as possible impact on the network as possible (i.e. the server may run something like a webserver already). It should be as easy to install and administer as possible.

What are the possibilities to achieve this using Delphi (Client: D7, Server up to D2010)?

Thanks to all for your suggestions. – Uwe Raabe Nov 14 '09 at 15:34 — Uwe Raabe, Nov 14 '09 at 15:34

score 5 · Answer 1 · answered Nov 13 '09 at 17:05

5

I use the Synapse library for such a simple server. Its lightning fast, very light, and threads easily. The demo Echo in the main synapse install is a fantastic start for what your trying to do. If you are going to be performing database access inside each request/response thread then I strongly also suggest looking at the connection pool example by Cary Jensen to keep your database connections in check.

answered Nov 13 '09 at 17:05

skamradt

15,366
2
36
53

Given the download page Synapse has still only experimental D2009 support. This doesn't give much confidence IMHO. – Uwe Raabe Nov 14 '09 at 10:25

score 5 · Answer 2 · answered Nov 13 '09 at 17:31

5

TCP, definitely. But I'd like to give a vote for ICS. Never liked Indy ...

answered Nov 13 '09 at 17:31

gabr

26,580
9
75
141

ICS and Indy seem to be quite comparable. Can you elaborate WHY you never liked Indy? – Uwe Raabe Nov 14 '09 at 10:29
ICS is completely asynchronous and that fits the TCP/IP model better. – gabr Nov 14 '09 at 21:03

score 4 · Accepted Answer · answered Nov 13 '09 at 14:09

4

What about Indy's TIdTCPServer and TIdTCPClient? They provide command handlers, which makes implementing text-based protocols very straight-forward.

answered Nov 13 '09 at 14:09

jpfollenius

16,456
10
90
156

score 2 · Answer 4 · edited May 23 '17 at 12:11

2

There are a lot of options.

Ultimately, I agree with Smasher and like using sockets. They're quick, easy and portable. If you're dealing with a fairly simple protocol and don't need a full n-tier solution, creating a TCP or HTTP server application is dead simple, very light weight, and easy to make compatible with any client. You can even add SSL support to these stand alone applications without having to configure a web server or interfering with it, if it's already running on the same box.

edited May 23 '17 at 12:11

Community

1
1

answered Nov 13 '09 at 14:19

Bruce McGee

15,076
6
55
70

The SSL is an interesting idea. – Uwe Raabe Nov 13 '09 at 14:27
It's one less external requirement for my application to worry about. I like XCopy install for servers as much as I do for client apps. :) – Bruce McGee Nov 13 '09 at 14:33

score 0 · Answer 5 · answered Nov 17 '09 at 11:14

0

I use RemObjects SDK for this sort of purpose. It takes care of all the difficult stuff, and I just ask it to connect and make function calls to pass the data.

answered Nov 17 '09 at 11:14

mj2008

6,647
2
38
56

What are the ways of interchanging string data between clients and a server in Delphi?

5 Answers5