> 3) Changing the application to work with GetASync(). That is defenitely the way to go.
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be ----- Original Message ----- From: "Carsten Muencheberg" <[EMAIL PROTECTED]> To: "ICS support mailing" <twsocket@elists.org> Sent: Monday, May 22, 2006 7:12 PM Subject: Re: [twsocket] thread message loop question > Arno Garrels wrote: > > Fastream Technologies wrote: > >> I think he is not assigning his own message oump at all--using the default > >> one with PeekMessage. > > [...] > > However, if he has both property MultiThreaded set to TRUE as > > well as calls (sync) method Get then it may result in plenty > > of CPU usage: > > Sorry, I may have caused some confusion. It is exactly like you say, > I am using Get() with MultiThreaded = true. In all other cases it workes > fine. > > So, I see three options here: > > 1) Leave it, like it is. This may confuse or concern some users though, > if they see the 100% CPU. > > 2) Adding the Sleep(1) hack to the OnDocData event. > > 3) Changing the application to work with GetASync(). > > Thanks again, I learned a lot. > Carsten > -- > 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 -- 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
