On 12-Aug-09, at 3:43 PM, Brett Porter wrote:
On 12/08/2009, at 5:58 PM, Jason van Zyl wrote:
John,
Not John, but I like to think I do a good impression :)
What's the range of features across the two http Wagon's right now?
They really don't do anything more than the underlying httpclient /
JDK implementations. HTTP Headers, connection timeout, and then any
parameters supported by HTTPClient in that version.
I assume in some cases we need the functionality of one versus the
other so I would just like to improve the Jetty-client based Wagon
and fix up what's required there,
I assume you mean the existing mercury-wagon (and its mercury deps),
not a new wagon based on the underlying jetty http client?
add any functionality and toss the other two.
shouldn't maven 3 equally support switching implementations and
instead choosing the new one as a default / only built-in /
supported impl?
I would like to have one good implementation and we can take
advantage of the parallelization, PGP, and SSL support in the Jetty
client.
I'm still not convinced doing the PGP this low down in the stack is
a good idea, I'd prefer it got fixed up in the core artifact
handling so it could be configured from the core and used in scp, etc.
I'm not convinced anyone cares about anything beyond http/s for
consumption. I think doing one implementation correctly which is
supportable is the first goal. Doing everything and trying to support
everyone is categorically a mistake.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/SonatypeNexus
http://twitter.com/SonatypeM2E
----------------------------------------------------------
Three may keep a secret if two of them are dead.
-- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
