[
https://issues.apache.org/activemq/browse/SM-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40841
]
Bruce Snyder commented on SM-1169:
----------------------------------
After pondering the state of HTTP in SMX a bit more, I'm thinking that the
servicemix-http component should be refactored to be more flexible so it can
handle multiple use cases instead of just addressing the SSL needs at present.
Currently there are multiple implementations for handling HTTP in SMX, each
with a different use case:
* the lightweight HTTP component - not JBI compliant
* the servicemix-http component's old endpoints - JBI compliant but not very
efficient
* the servicemix-http component's new endpoints - JBI compliant and more
efficient but doesn't support SSL so it is being refactored
* the servicemix-cxf-bc - handles the HTTP use case for the servicemix-cxf-se
And we still need to address the following use cases:
* asynchronous HTTP as well (this is supported by the Jakarta Commons HTTP
Client 4.x alpha release (see
[HTTPCORE-10|http://issues.apache.org/jira/browse/HTTPCORE-10] for more info))
* REST style use cases (not sure if this one can be addressed in just the
servicemix-http component or if it's much wider than that)
I've been thinking that the real solution to all of this is a more flexible
design in the servicemix-http component so that each use case is handled by a
different strategy. We may have to use two levels of configuration in in the
{{xbean.xml}} when configuring it, but I think we could do this by allowing:
# generic HTTP configuration for the component
# use case specific configuration to determine the strategy to be used
What are your thoughts on this?
> Provide support for using a JHC client in the http provider endpoint
> --------------------------------------------------------------------
>
> Key: SM-1169
> URL: https://issues.apache.org/activemq/browse/SM-1169
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-http
> Affects Versions: 3.3
> Reporter: Adrian Co
> Assignee: Bruce Snyder
> Fix For: 3.3
>
> Attachments: http-provider.patch
>
>
> Current http client in the new http provider endpoint uses the jetty client,
> which does not support ssl or proxy. Using the new JHC client supports both
> ssl and proxy. Also, creating a client api to plug the nio implementation of
> the jhc might be useful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
