[
https://issues.apache.org/jira/browse/DISPATCH-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305864#comment-14305864
]
Rafael H. Schloming commented on DISPATCH-103:
----------------------------------------------
I would look at proton-c/src/framing/* and proton-c/src/transport/*. You are in
for a treat as this is one of the older and cruftier parts of the codebase. I
believe Andrew is working in this area on SASL support and probably doing other
cleanups as well. You may want to talk to him as he did the autodetect stuff
and had some thoughts about how to splice in web sockets.
I actually think the bulk of the work here is probably the web sockets
implementation itself. I looked a month or two ago and I couldn't find much in
the way of good options for existing implementations. What is available in C
seems to be either incomplete/abandoned or just a straight proxy implementation
without actually exposing any sort of library. I looked briefly at implementing
the web sockets stuff from scratc (the framing is pretty straightforward) but
there's actually more complications than you might think in the
handshake/negotiation stuff. (Apparently there are a lot of different versions
of web sockets.)
If you find/write something that has a decent protocol-engine style interface,
e.g. something simple that you lets you read/write websocket messages into/out
of the "top half" and then lets you read/write bytes from the "bottom half", I
can probably help you integrate it into the transport quite easily.
> Websocket Listeners
> -------------------
>
> Key: DISPATCH-103
> URL: https://issues.apache.org/jira/browse/DISPATCH-103
> Project: Qpid Dispatch
> Issue Type: New Feature
> Components: Container
> Reporter: Ted Ross
> Assignee: Alan Conway
> Fix For: 0.5
>
>
> Add an option in configured listeners to use websockets encapsulation. This
> will allow AMQP clients inside web browsers to directly connect to the
> message bus.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
