Hi Angus,
Thank you for your comments re the TIcsWndControl exception. I will look out for this and report anything I encounter in this area. I am currently using 300 clients per thread on the multithreaded server component but am not sure how many threads (and therefore message pumps) are actually created and destroyed, so am not sure if I am already past you 100K limit, or just nowhere near reaching that limit - time will tell. (I assume that you are using a single thread per connection). Thanks for the info re the restarting the service (I was thinking along the lines of a monitoring app to monitor, kill (if necessary) and restart the service as required) but your method is a really slim implementation that achieves most of what I am trying to do. Last week I was convinced that I would need the ability to forcibly kill the task when things went pear shaped, but now things look so stable, and I don't think it will be necessary. Also, thanks for the info on your mail queue component, I like your methodology (making it bulletproof - regardless of what happens with the application). Thanks for your input, all very much appreciated. Regards, Tim -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
