If I remember correctly, if the server took more than 60 seconds or so to return the entire list of information, we would get the error. I never thought about the server timing out and disconnecting....Very Interesting....
-- Thank you, Mike Minor Z-Code Systems, Inc. [EMAIL PROTECTED] "Denver Braughler" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Mike Minor wrote: > > ... in my case they occurred when a call was made to go get a large > > amount of data via DDP from a DSM system. If the DSM system, or the > > network itself was running slow, if the data was not returned to the > > calling page quickly enough, we got these errors. > > That's interesting. > I am not aware of nor do I believe that there is any time limit on the client side. > But the HTTP/TCP session could be dropping out when the network is overloaded. > > Are you talking about a really long time, minutes not seconds? > Perhaps were you hitting your server's autodisconnect time out?
