qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rafael Schloming <...@alum.mit.edu>
Subject Re: [Fwd: [jira] [Commented] (DISPATCH-103) Websocket Listeners]
Date Fri, 06 Feb 2015 14:50:42 GMT
On Fri, Feb 6, 2015 at 9:28 AM, Alan Conway <aconway@redhat.com> wrote:

> On Fri, 2015-02-06 at 08:19 -0500, Rafael Schloming wrote:
> > A couple of questions/comments inline, but first off, any reason this
> > isn't on the list? (I don't mind, just curious.)
> No good reason, including list now.
> Extremely useful discussion, thanks! Taking it all on board.
> New question: For dispatch I only care about the server side. JavaScript
> is the only websocket client I know of and as per discussion below we
> would actually need to *exclude* proton client-side websocket support
> from the JS client, so maybe we don't need it at all. Are there use
> cases for a websocket client transport?

The main use case I know of for non-browser websocket *client* use is
firewall traversal. I think you can also do this by simply using SSL
though, although there may be some corner cases where that does't work as

I think the main benefit of building it out in proton though is to get more
uniform support for it on proton based servers, e.g. if proton can just
autodetect it, then it should be pretty trivial to support it in qpidd as
well as dispatch.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message