I see no reason why it would not be accepted. First, you are implementing
an already existing API abstraction, and second, I would assume that you are
not changing backwards compatibility. And most important, you are
scratching the itch ;-)
Scott
----- Original Message -----
From: "Vincent Massol" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 23, 2001 9:30 AM
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 ... :)
>
> Thanks
> -Vincent
>
> ----- Original Message -----
> From: "Daniel Rall" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Cc: "Vincent Massol" <[EMAIL PROTECTED]>
> Sent: Thursday, August 23, 2001 5:04 PM
> Subject: Re: HttpClient and HttpURLConnection ?
>
>
> > "Vincent Massol" <[EMAIL PROTECTED]> writes:
> >
> > > I would need to use commons-httpclient in Cactus. However, I don't
want
> to
> > > change all my code and especially I may want to continue JDK 1.4
> > > HttpURLConnection in the future (if it is corrected) as I have a very
> simple
> > > need.
> > >
> > > Could I submit a HttpURLConnection class for commons-httpclient that
> would
> > > be a wrapper around HttpClient and others and would implement
> > > java.net.HttpURLConnection ?
> >
> > I have nothing to do with that project, but your suggestion sounds
> > like a great idea to me.
> >
>
>
