Posted by Brian Levantine on September 05, 2007 at 11:53:28:
In Reply to: Comet time-out posted by greg on September 04, 2007 at 09:36:25:
Comet uses the default Winsock settings for timeouts which is 30 seconds. When we get a timeout error, it is reported by Winsock and we give up immediately because there may be other components that rely on prompt responses (within the timeout limits, of course) that will eventually fail also. If one stops, all of those waiting will also timeout, making a "retry" dialog a unsatisfactory solution. The problem can also occur in the opposite direction. That is, the server can timeout waiting for a response from a client. No way to even think about a "retry" dialog there. This product was never intended to operate under such unreliable conditions and as such there's not much we can do without a major redesign. I suspect there is some other part of your network that is not recovering properly from the short interuption. I will however, perform some tests to make sure that our code is not doing something that would cause a failure for such small delays. We'll post on the forum something if there does in fact turn out to be a problem on our end.