Re: [twsocket] Troubles with using TPing in multithreadedapps(DnsLookupDone er

2007-01-07 Thread Arno Garrels
Angus Robertson - Magenta Systems Ltd wrote:
 I haven't looked at the source, but usually a working message pump
 is required in a worker thread to make asynchronous events working.
 That most likely applies to the Ping-component as well
 
 Ping/ICMP is a blocking function, which is the main reason for my ping
 component running it in a thread.  Since it's running in a thread,
 there is no point in doing an asynchrous DNS lookup, so my component
 does a much simpler blocking DNS lookup (or reverse lookup), to avoid
 needing a message pump.

I already guessed something similar, so probably running your component
in multiple threads isn't required since it already creates worker threads
as necessary, right?

--
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


Re: [twsocket] Troubles with using TPing in multithreadedapps(DnsLookupDone er

2007-01-07 Thread Angus Robertson - Magenta Systems Ltd
 I already guessed something similar, so probably running your 
 component in multiple threads isn't required since it already
 creates worker threads as necessary, right?

Absolutely, no reason to complicate the application with more code in
threads than really necessary, just the ping and DNS lookup. 

Angus
-- 
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