On 21 Jan 99, at 19:51, Stefan Franke wrote:
When I run Zope using ZopeHTTPServer on my Win NT4 SP3 Box (both multi and single threaded) I get lots of winsock error-exceptions like those below, when I open the management screen with any browser and click the reload button very heavily (or synchronously on two machines even not so heavily). Is this normal, due to interrupted requests? I've no idea about socket communication (my knowledge start on the http text stream level) so this could just be an upset naive "Oh my God, this Red Light started flashing" post.
error: (10054, 'winsock error')
This error is "connection reset by peer". Those nasty web clients are doing an abortive close on their sockets, so the connection is "aborted" rather than gracefully closed. This is going to happen *a lot*, (anytime someone presses STOP on their browser). I think it would be good if ZopeHTTPServer would *not* generate a traceback for this error, just ignore it and treat is as "connection closed". Brad Clements, bkc@murkworks.com (315)268-1000 http://www.murkworks.com (315)268-9812 Fax netmeeting: ils://ils.murkworks.com ICQ: 14856937 We must come down from our heights, and leave our straight paths, for the byways and low places of life, if we would learn truths by strong contrasts; and in hovels, in forecastles, and among our own outcasts in foreign lands, see what has been wrought upon our fellow-creatures by accident, hardship, or vice. - Richard Henry Dana, Jr. 1836