[
https://issues.apache.org/jira/browse/PROTON-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neeraj Makam updated PROTON-1569:
---------------------------------
Summary: Proton-j: Handle connections through a proxy server using
websocket (was: Proton-j: Handle connections through a proxy server using web
socket)
> Proton-j: Handle connections through a proxy server using websocket
> -------------------------------------------------------------------
>
> Key: PROTON-1569
> URL: https://issues.apache.org/jira/browse/PROTON-1569
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
> Affects Versions: Future
> Reporter: Neeraj Makam
>
> Is there a way to use web sockets as a transport layer for proton-j?
> My main use cases for this request -
> 1. Being able to route traffic through 443 port instead of AMQP ports.
> 2. Being able to connect to messaging brokers from a machine behind a proxy
> server.
> I see that there are already two issues for the same which are closed right
> now. I also see that through "TransportInternal" interface, we can extend our
> own transport layer. But this requires me to implement my own frame handling
> for web sockets. Instead, what I'm looking for is being able to integrate a
> third party java websocket implementation (say
> [jetty|http://www.eclipse.org/jetty/] as the transport layer which takes care
> of all web-socket intricacies. Is there a way I can replace the transport
> layer to something else?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
