Fastream Technologies wrote: > ----- Original Message ----- > From: "Arno Garrels" <[EMAIL PROTECTED]> > To: "ICS support mailing" <twsocket@elists.org> > Sent: Wednesday, May 17, 2006 5:03 PM > Subject: Re: [twsocket] thread message loop question > > >> Fastream Technologies wrote: >>> >>> I suggest you to add a simple Sleep(1) to the message pump >> >> This would result in very poor performance, it's really not >> recommended, even though it works ;-) >> >> For a simple message loop have a look at CtrlSocket.MessageLoop, >> it is the built-in message pump that you can call. Property >> CtrlSocket represents the underlying TWSocket instance, > > This is already called internally with Get() and it should be > fixed with GetMessage.
TWSocket.MessageLoop uses GetMessage(), I don't see a problem. No need to call Sleep() since GetMessage() waits for a message before it returns, this wait uses zero CPU time. --- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
