Hi Paul Hmm. I thought the application process messages might be screwing things up. I just needed it confirming.
Each time my webserver needs to "nudge" one of the other applications then I guess I should start a thread to do this. The "other" applications simply come to life when "nudged" by the webserver app. The apps are on different systems hence the use Of a socket to nudge it. Regards Chris -----Original Message----- From: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] On Behalf Of Paul Sent: 07 December 2009 14:36 To: ICS support mailing Subject: Re: [twsocket] Use of twsocket in thttpserver application > My socket connection to other programs is done in the main thread. Should not be a problem, but it could slow down the server. > > After I call connect I call application processmessages until I get > connected and then I close. > Do you think this could be "interfering" with the HttpServer component > logic? Calling Application.ProcessMessages is very dangerous and is not neccesary at all. I could disturb the message pumps used by all async components. It is most likely the cause of the problems you have. Paul -- 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 -- 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
