Francois Piette wrote: > You should always implement timeout. Altough in your particular case, there > may be a problem somewhere else. Good to know! Is there a "magic number" for the default timeout? What should we use? Is it worth using different time-out's for different stages of connection? Ex: use a long timeout for DNS queryes, use shorter timeout for the connection itself, use long timeouts for data transmission itself? > I suggest you use a sniffer to see why the > connection doesn't establish with the webserver (The next state after > httpDnsLookupDone is the connection). Using a sniffer (I suggest Ethereal, > link from the links page at ICS website), you'll be able to see if the > connection request packet is sent by your program and if the reply (positive > or refused) come back from server. I guess the reply doesn't come back. Once > we know that information, we'll be able to diagnose further. > I took your advice and I downloaded ethereal, and that (almost) solved my problem. I wasn't able to actually get the system to fail while under the microscope but I did learn two valuable peaces of information: (1) I'm not only connecting to the http server on my LAN, I'm also connecting to a http server very far away (my site is hosted in New York, I live in Romania so it's almost on the other side of the world) (2) Ethereal showed clear signs of bad connections: duplicate ACK's, retransmissions, packets lost!
So that's the end of it. It's the server that's causing my troubles... Thanks for your help! Cosmin Prund -- 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
