[ 
http://jira.codehaus.org/browse/MNG-4306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason van Zyl updated MNG-4306:
-------------------------------

    Description: 
We need a new high performance Wagon that encapsulates all the features of the 
current HTTP wagons, but will be the single implementation we use going forward.

Brian's comments on the features of each Wagon right now:

Currently the lightweight impl handles NTLMv2 and does a better job
caching the data when the repository asks for authentication (this one
uses Sun code). The Sun code has bugs that interfere with uuencoding
of data in the headers, specifically the passwords. The other wagon
uses the httpclient, which doesn't support NTLMv2 and doesn't cache
the data, screwing up the stream observers with repos that need auth.
It doesn't screw up the data in the headers. So hopefully Jetty will
support NTLMv2, be smart about handling authenticated repos and not
screw up the data in the headers.


  was:We need a new high performance Wagon that encapsulates all the features 
of the current HTTP wagons, but will be the single implementation we use going 
forward.


> Jetty-client based Wagon
> ------------------------
>
>                 Key: MNG-4306
>                 URL: http://jira.codehaus.org/browse/MNG-4306
>             Project: Maven 2
>          Issue Type: New Feature
>            Reporter: Jason van Zyl
>            Assignee: Jesse McConnell
>             Fix For: 3.0-alpha-4
>
>
> We need a new high performance Wagon that encapsulates all the features of 
> the current HTTP wagons, but will be the single implementation we use going 
> forward.
> Brian's comments on the features of each Wagon right now:
> Currently the lightweight impl handles NTLMv2 and does a better job
> caching the data when the repository asks for authentication (this one
> uses Sun code). The Sun code has bugs that interfere with uuencoding
> of data in the headers, specifically the passwords. The other wagon
> uses the httpclient, which doesn't support NTLMv2 and doesn't cache
> the data, screwing up the stream observers with repos that need auth.
> It doesn't screw up the data in the headers. So hopefully Jetty will
> support NTLMv2, be smart about handling authenticated repos and not
> screw up the data in the headers.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to