I have used Indy quite a bit. Yes, it is a PITA, and their use of exceptions to signal various trivial things to the rest of the library is completely lame. Their tech support ranges from third rate to downright hostile. When their tech support guy is taking his proper medications, you can sometimes get a useful answer to your questions. :-)
That being said, it works, it's free and it handles just about any standard protocol. It is easy to create your own TCP/IP or UDP protocols too, if that is your thing. I have used it in several major projects (> 1 million lines of code). I use it for POP3 email, HTML spidering, HTTPS, FTP clients and servers, SMTP clients and servers and encrypted telemetry over TCP/IP. I created my own protocol for the encrypted telemetry project - I needed a very low bandwidth solution that would work over a narrow band VHF data-over-voice channel. Try doing TCP/IP at 9600 baud some time. Anyway, once you work with Indy for a while, you can accomplish just about anything - it just takes a while to crawl up the learning curve. I have used ICS a couple times, but always find myself going back to Indy. ICS is pretty bare bones. I have not used TSocket. > > Greetings from Shailendra. > > I have two question to ask. > > 1 )i am developing online chat massanger application. I have developed two > simple applicaiton using Indy Component and TServerSocket/ TclientSocket > component. Before enhacing same applicaiton I need advice from you people. > please advice which components component I should used. Application should > have webcam and voice enable. Is it better to use Tsocket or Indy ? > > 2 ) to make use of WebCam /voice which is the best library / component. > > Thanks in advance > > Regards > S K Singh > 9810560080 >
