Hi:
This changes was suggested by Peter Hunsberger:
Overview: =========
When Cocoon attempt to close an already closed stream you get an IO exception. If the user keeps closing the session the error doesn't tell you why, just that it happened. If it's an error on the client side and I personally can't see that I care about it on the server (Cocoon) side.
A full discussion here: http://marc.theaimsgroup.com/?t=107463769600001&r=1&w=2
Here is the vote:
1- [+1] Cocoon will don't throw any exception when this happen. 2- [-1] Log the event at INFO level. 3- [+1] Log the event at DEBUG level.
*IMPORTANT*
------------
IIRC this is at least the *fourth* time this is discussed and changed since I've been on this list. Thus I *highly* recommend that the decision and motives of this vote are included in the comments of the file and that a unit test is written, also with the same comments, that checks that this decision is enforced.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------