> for details) when the client closes the tcp connection prematurely, the
> python process/thread runniung the servlet starts looping with 100% cpu
> usage.
Ok, I have confirmed that the problem occurrs with mod_webkit aswell.
Also, I have been trying to understand what might be going on. But I cannot
for the life of me find the location in the code where the data actually gets
sent to the client.
HTTPResponse.write() does write the data to _strmOut, but that is a
TASASStreamOut according to the debug output I put in before the write(). The
TASASStreamOut class only puts data in an in-memory buffer (even when
flushing) and I cannot locate where that data is actually pulled out of the
stream and sent to the socket.
In either case, it is clear that
def createResponseInTransaction(self, transaction, strmOut):
response = self._responseClass(transaction, strmOut)
transaction.setResponse(response)
return response
of Application is giving the actual socket (strmOut) to the response class
which I assume is HTTPResponse (though I can't find it). The constructor of
HTTPResponse passes strmOut to the parent - Response - which sets the
_strmOut instance variable. So it looks to me that trans.response()._strmOut
should be the socket, yet when I attempt to verify that I get a
TASASStramOut, and I have no clue where it came from.
Perhaps someone more knowledgable can explain where I'm going wrong?
--
/ Peter Schuller, InfiDyne Technologies HB
PGP userID: 0xE9758B7D or 'Peter Schuller <[EMAIL PROTECTED]>'
Key retrival: Send an E-Mail to [EMAIL PROTECTED]
E-Mail: [EMAIL PROTECTED] Web: http://www.scode.org
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss
