13 Jul
1999
13 Jul
'99
3:42 p.m.
I've been comparing the streaming output of ZServer and ZopeHTTPServer , and come across two disadvantages related to the way ZServer buffers writes in memory. Firstly if the output is created faster than the client can consume it then the Zope process grows to accomodate the buffer. If the streamed output is large then this may not be appropriate. Secondly, there seems to be no convenient way to abort the method if the client disconnects part way through receiving the streamed output. With ZopeHTTPServer in this situation, RESPONSE.write would raise an exception. Is there anyway to recover some of the old behaviour under ZServer?