Posted by Mike Saunders on September 10, 2007 at 11:11:16:
In Reply to: Re: Comet time-out posted by Brian Levantine on September 10, 2007 at 09:35:49:
For additional reference...
As Greg has not chimed in here again, with more discussion on his symptoms, I am not sure what we have been discussing is the same as he is seeing. He stated.... even for a second...
My original response was because Jim gave the impression that he could disconnect the network cable and reconnect with out a problem, and I wanted that clarified. (I was not trying infer that I thought that the 4-7 seconds was a problem, as I do not.)
====================================
Our Q-World Terminal emulation client/Server product also uses TCP and has the same symptoms. i.e. error 10054 after about 7 seconds. Pretty sure we had a similiar discussion on an autoreconnect and apparently decided against it. If I recall, loosing sync between the state of the client screens and where the Q-world system thinks it is was a big part of the reason.
However, for ours the actual program was running on the Q-world system.
So the client did not really know where it was in the program.
Under Comet things are different.
Side commment.... end users say, look my internet is fine....so my network is good... why does Comet(or LEWin32) keep dropping...
They do not realize the differences in communication methods that come into play.