----- Original Message -----
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; "Vincent Massol"
<[EMAIL PROTECTED]>
Sent: Thursday, August 23, 2001 5:53 PM
Subject: Re: HttpClient and HttpURLConnection ?
>
>
> On Thu, 23 Aug 2001, Vincent Massol wrote:
>
> > Date: Thu, 23 Aug 2001 17:30:36 +0100
> > From: Vincent Massol <[EMAIL PROTECTED]>
> > Reply-To: [EMAIL PROTECTED],
> > Vincent Massol <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Subject: Re: HttpClient and HttpURLConnection ?
> >
> > thanks, I'd also like to have some feedback from commons-httpclient
> > committers ... I'm in the midst of writing it (almost there) and would
hate
> > to have to throw away my work if the idea is not accepted ... :)
> >
>
> In concept, I think its a neat idea (and something I'm sure lots of
> container vendors have to deal with as well, if they use HTTP connections
> internally).
>
> I'm not (yet) a user or developer of httpclient, so consider this a
> non-binding +1.
>
Thanks. I have started writing it. I'm focusing on providing the same
behaviour as java.net.HttpURLConnection for "standard" use cases. That would
be the hard part : providing the same behaviour for all cases ... (except
for bugs :) ). Like calling getInputStream() will make the call to connect()
if you haven't done so, ...
Another reason why I really need to use HttpClient through HttpURLConnection
is that in Cacus, we integrate with HttpUnit to benefit from it's HTML/XML
parsing feature for the returned server stream ... and HttpUnit only accepts
a HttpURLConnection ...
Thanks
-Vincent
