15 Apr
2010
15 Apr
'10
3:33 p.m.
On Thu, Apr 15, 2010 at 09:25:41AM +0200, Attila Lendvai wrote:
i've done a bit more experimenting and i have one more data point: firebug in ff shows that the http request is running indefinitely long (several minutes later the progress indicator still spinning), even though the server log shows that handling the request have finished (with a call to close in uwp and no sign or error). maybe the browser does not receive the socket closed notification?
I've seen that exact error. My example programs will produce it. Just start up ex6-server, connect with ex5a-client, type 'hello' at the client prompt, then 'quit'. The client hangs around forever while the server closed the connection.
-pete