how can i manage connections in Indy ? (Delphi)

i am writing a simple client/server chat program with indy 10 (blocking mode) and there is a question that how can i manage connections ? for example imagi开发者_如何学JAVAne a user that is online on server , we must make a connection tunnel for future requests . In other words, when a user is online server should not need username and password for future user requests . and it will be do with the tunnel that we created when user has came .

how can we manage connections ?

[sorry for my bad english] if you can't understand me please tell me to send a new post agian .

Thank you

For the scenario described in the question, there isn't really much management to do. To avoid having to re-authenticate on every request, simply don't close the connection. In a chat server, especially, it's quite likely that each participant will establish a connection and then continue using that same connection for the duration of the chat.

Indy server objects already keep a list of their open connections, so when you want to broadcast a chat message to the other participants, you can just iterate over that list.

I think 100000 checks per second will be the less resource consuming thing, than having 10000 persistent TCP connections. And anyway you will need to process somehow these 100000 commands, so those checks would not be the bottleneck.

Try to use the UDP messages instead. For example, most MMO games use both TCP and UDP connections. TCP only for critical data, and UDP for any other data. In your case UDP seems to be acceptable. The client can send UDP packets with some autoincrement IDs, and the server can periodically send back the list of IDs it doesn't receive, so the client can resend them.

One option would be to create a unique session ID (or "token") on the server side, for example a GUID, if a client logs in. And in every request, the client includes this token.

The server would maintain a list of client sessions and associated session data, and looks up the token in this list.

Even if a client is temporary disconnected from the Internet but still knows its token, the application can reconnect and continue the session with the server.