DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21754>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21754 NullPointerException when releasing connection ------- Additional Comments From [EMAIL PROTECTED] 2003-07-21 07:28 ------- Laura, I can be used separately and needs to be public so that you can implement your own connection manager anyway. The catch is that if you use it separately instead of through HttpClient you miss out on most of the benefits of HttpClient and are going to have a hard time following all the contracts for managing connections as well as keeping up with internal changes to HttpClient. Basically, you can go down that route (and I believe you did for quite some time by necessity) but you're pretty much on your own and are likely to hit trouble. It is definitely possible though. Generally it's better to add whatever flexibility you need to HttpClient instead of doing away with it. That's my thoughts on it anyway. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
