Hi, Nelson! You're right! I've downloaded the latest Mozilla build and it's working perfectly! I was thinking exactly about this kind of problem, because in time of Mozilla's silence with second connection, I've seen two TCP connections established in 'netstat -na' output, which doesn't make sence since I've called closesocket() and it returned success.
Can I bother you with couple of questions more? Maybe there some workaround is existing for this problem? I mean maybe I can do something in my server to make Mozilla close the prev. connection and open a new one? (both the server and Mozilla are running on Windows) And the last question: in which version of Netscape those corrections will be available? Thank you very much for your big help! Nelson B. Bolyard wrote:
One more thing. I suspect that mozilla is not noticing that the second
connection is connected. That code has been changed since 1.2b. Would you be willing to try a nightly build of mozilla to see if the problem is already fixed in one of those?
--
Nelson Bolyard Disclaimer: I speak for myself, not for Netscape
