hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Moran <mike_mo...@mac.com>
Subject Re: DO NOT REPLY [Bug 21754] - NullPointerException when releasing connection
Date Mon, 21 Jul 2003 07:53:59 GMT

On Monday, Jul 21, 2003, at 08:28 Europe/London, bugzilla@apache.org 
wrote:
[ ... ]
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21754
>
> NullPointerException when releasing connection
>
[ ... ]
> ------- Additional Comments From adrian@ephox.com  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.

Is that the general development strategy? I ask since I am about to try 
to integrate the HttpClient 2.0 beta 2 into an existing framework. I 
would be doing this to benefit from robust and performant communication 
with servers, not from features provided by the HttpClient class. For 
exaple, regardless of whether the HttpClient class handles redirects 
properly now, I will never use it to transparently handle them as I 
need to see them and handle them myself.

If I am to be forever doomed to continual revisions due to 'internal' 
api changes because I don't go through the HttpClient class then I may 
have to reconsider whether I can use the library.

After reading through 
"http://jakarta.apache.org/commons/httpclient/tutorial.html" I see that 
there is no distinction made between "HttpClient" the library and 
"HttpClient" the class. Is this deliberate?

Sorry for beating on you people for this, and I realise I am probably 
in a minority, but there is not much point in me going down this route 
if I am destined to have to drop it all.

Ta,

-- 
Mike


Mime
View raw message