Best Component for Client-server with thousands client [closed]

Question

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 8 years ago.

What is the best Component for a Client-Server (TCP) application with thousands of clients involved whereas all connections must stay alive ?
So far I have used Indy with one TIdTCPServer in the server application and one TIdTCPClient in all of the client applications. I want both the clients and the server to send data at any time and any size.
Is this a good approach?

Answer 1

It might work, but it might also end up with a lot of problems depending on what kind data, load, security and so on. I ended up using a web server (Tomcat + Comet). The work is already done : socket stability, framework, security, load sharing across several instance etc... A thousands of client is not that easy to handle... And then you can focus on your application, and only on it.