You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Adrian Co (JIRA)" <ji...@apache.org> on 2007/12/13 07:32:26 UTC
[jira] Created: (SM-1169) Provide support for using a JHC client in
the http provider endpoint
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.
[jira] Updated: (SMXCOMP-77) Provide support for using a JHC client
in the http provider endpoint
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen updated SMXCOMP-77:
-----------------------------------
Fix Version/s: (was: servicemix-http-2009.02)
servicemix-http-2010.01
> Provide support for using a JHC client in the http provider endpoint
> --------------------------------------------------------------------
>
> Key: SMXCOMP-77
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-77
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-http
> Affects Versions: 3.2.3
> Reporter: Adrian Co
> Assignee: Bruce Snyder
> Fix For: servicemix-http-2010.01
>
> 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.
[jira] Commented: (SM-1169) Provide support for using a JHC client
in the http provider endpoint
Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (SMXCOMP-77) Provide support for using a JHC client
in the http provider endpoint
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann updated SMXCOMP-77:
----------------------------------
Fix Version/s: (was: servicemix-http-2009.01)
servicemix-http-2009.02
> Provide support for using a JHC client in the http provider endpoint
> --------------------------------------------------------------------
>
> Key: SMXCOMP-77
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-77
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-http
> Affects Versions: 3.2.3
> Reporter: Adrian Co
> Assignee: Bruce Snyder
> Fix For: servicemix-http-2009.02
>
> 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.
[jira] Commented: (SM-1169) Provide support for using a JHC client
in the http provider endpoint
Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40928 ]
Bruce Snyder commented on SM-1169:
----------------------------------
{quote}
Support for virtual host by name- Should these be separate services?
http://companyA.com:8080/serviceA/
http://companyB.com:8080/serviceA/
{quote}
Are you referring to a single host providing both TLDs? And because both domains are provided by the same host, then you're asking if serviceA should be the same instance or a different instance for each domain? If that's what you're asking, I'd argue that each domain should have it's own instance of serviceA.
> 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.
[jira] Commented: (SM-1169) Provide support for using a JHC client
in the http provider endpoint
Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40922 ]
Bruce Snyder commented on SM-1169:
----------------------------------
Another use case was just mentioned on the user mailing list regarding the support of multiple endpoints being allow to share the same port number. E.g., below are two URLs to demonstrate this use case:
* http://example.com:1234/serviceA/endpoint1/
* http://example.com:1234/serviceB/endpoint1/
Currently the servicemix-http component does not support this but it should.
> 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.
[jira] Commented: (SM-1169) Provide support for using a JHC client
in the http provider endpoint
Posted by "Matt Pavlovich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40927 ]
Matt Pavlovich commented on SM-1169:
------------------------------------
A couple of other use cases:
Support for virtual host by name- Should these be separate services?
http://companyA.com:8080/serviceA/
http://companyB.com:8080/serviceA/
SSL - Should be by IP+port, and allow multiple services on that IP+port combo
Same SSL cert:
https://192.168.1.1:8080/serviceA/
https://192.168.1.1:8080/serviceB/
https://192.168.1.1:8080/serviceC/
Different SSL cert. Different service?
https://192.168.1.1:8192/serviceA/
https://192.168.1.2:8080/serviceA/ (Note: the ".2" ip addr)
And of course support combinations..
Different services?
http://companyA.com:8080/serviceA/
https://192.168.1.1:8080/serviceA/
http://companyB.com:8080/serviceA/
> 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.
[jira] Updated: (SM-1169) Provide support for using a JHC client in
the http provider endpoint
Posted by "Adrian Co (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Co updated SM-1169:
--------------------------
Attachment: http-provider.patch
Attaching implementation for review
> 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.
[jira] Updated: (SM-1169) Provide support for using a JHC client in
the http provider endpoint
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang updated SM-1169:
-----------------------------
Fix Version/s: 3.3.1
3.4
(was: 3.3)
> 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.1, 3.4
>
> 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.
[jira] Updated: (SMXCOMP-77) Provide support for using a JHC client
in the http provider endpoint
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated SMXCOMP-77:
----------------------------------------
Fix Version/s: (was: servicemix-http-2010.01)
servicemix-http-2010.02
> Provide support for using a JHC client in the http provider endpoint
> --------------------------------------------------------------------
>
> Key: SMXCOMP-77
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-77
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-http
> Affects Versions: 3.2.3
> Reporter: Adrian Co
> Assignee: Bruce Snyder
> Fix For: servicemix-http-2010.02
>
> 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.