Correct, the calling thread won't be blocked.
Arno,
I´m having a problem with a customer, and I sucessfully reproduced the same
problem here. I really believe that it is related to DNS Lookup. Here is
what is happening:
- I have a communication thread that spawns all TCP client sockets, so, all
communication messages are carried by this thread, not by the main thread
- I can have several instaces of TCP clients spawned by the communication
thread
The test that I did:
- I have some TCP sockets connected to fixed IP addresses and receiving
realtime video data (MPEG-4 video stream)
- When I try to connect to a DNS address from dnsalias.com, all the data
that was receiving from all TCP sockets stops for 2 seconds.
I believe that this time is the DNS lookup because if I try to ping the
address it takes about 2 seconds to resolve the address
You told me that the thread would not blobk, but it stops receiving all TCP
data during the DNS lookup?
Any idea on why does it happens?
If I make my own DNS lookup using threads, would it solve?
Thanks!
Eric
--
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
