[
https://issues.apache.org/jira/browse/CXF-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005858#comment-13005858
]
Daniel Kulp commented on CXF-291:
---------------------------------
The code was on a branch I created a long time ago:
http://svn.apache.org/repos/asf/cxf/branches/async-client/
with the specific code in:
http://svn.apache.org/repos/asf/cxf/branches/async-client/rt/transports/http/src/main/java/org/apache/cxf/transport/http/async/
That said, I started that all before 2.3.0 was released so it's definitely a
bit out of date and would need some refactoring. If I remember correctly, I
has most of the non-SSL cases working. I hadn't started on the SSL stuff at
all. Not really 100% possitive though. For the most part, it hasn't been a
priority as it didn't provide any major benefit over the HTTPURLConnection for
the normal CXF usecases and actually performs slightly slower. However, for
async calls, it could have some benefit. More details:
http://cxf.547215.n5.nabble.com/Async-HTTP-client-side-td2835428.html
> Support Commons HTTP Client for HTTP conduit
> --------------------------------------------
>
> Key: CXF-291
> URL: https://issues.apache.org/jira/browse/CXF-291
> Project: CXF
> Issue Type: New Feature
> Components: Transports
> Affects Versions: 2.0
> Reporter: Dan Diephouse
> Labels: gsoc2011
>
> I think commons http client is a must in terms of HTTP support as it supports
> a lot of different authentication modes that I don't know that we currently
> support. It shouldn't be that hard to integrate either. XFire users tend to
> depend pretty heavily on it. The XFire code can be found here:
> http://svn.xfire.codehaus.org/browse/xfire/trunk/xfire/xfire-core/src/main/org/codehaus/xfire/transport/http/CommonsHttpMessageSender.java
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
