Michael Becke wrote:
It seems that the connection wrapper solution will work. I will go ahead and and clean up the code some and submit a patch tonight or tomorrow. If anyone has suggestions/ideas about this change please let me know. In particular I would like to hear some comments regarding the following:
- what is a good name for this connection wrapping class, currently it is HttpConnectionAdapter?
PooledHttpConnection
- should this class be available outside of the MultiThreadedHttpConnectionManager?
No I think package access should be enough.
- once the wrapped connection has been released what should be the default behaviour for the connection methods? I was thinking any methods that perform I/O should throw an exception. Other methods would just return default/empty values or do nothing.NullPointerExceptions are fine too, if they occur due to improper use. So throwing away the intrinsic reference to the wrapped object will do.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
