Arno Garrels wrote: > Hi, > > I should have tested more carefully, sorry for that. > After some stress tests with the webserver for MacOS > I hit a bug today that I do not understand. > Once in some state Accept() returns a socket handle > with a port number that doesn't match the port number of > the connecting socket.
As a result the response is sent to the nirvana and the browser waits for a response infinitly. Obviously that socket handle is valid somehow but nobody is listing at its other end. -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
