tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 52593] outputbuffer.recycle() is called immediately after response instead of at socket close
Date Sun, 05 Feb 2012 20:48:23 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=52593

Mark Thomas <markt@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #1 from Mark Thomas <markt@apache.org> 2012-02-05 20:48:23 UTC ---
It is this way for several reasons:
- support for pipelined requests
- ensure correct recycling of objects after an error
- simpler code

Correctly determining when recycled() is required and isn't would require more
complexity to monitor connection state than the extra recycles currently used.

Further, the impact of not recycling is far worse than the impact of extra
recycling.

If there was a case where there were multiple recycle() calls and it was clear
that one or more was always unnecessary then there would be a case to remove
it. That is not the case here.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message