websocket over HTTP via JSON about autobahn-cpp

[jpetso]

As a suggestion, you might want to do rebases instead of merges if the intention is to get your branch merged back into upstream autobahn-cpp.

We've also recently split out https://github.com/tplgy/json-msgpack from bonefish which handles JSON/msgpack conversions with a minimal amount of extra copies, we should probably also move the WAMP-specific binary handling into that project and see if it can be switched to the Boost license as well.

[CepGamer]

May I ask you a couple of questions?

What would you recommend on how to implement switch between websocket frames and raw byte exchange via TCP?
Also, I'm using websocketpp to construct frames which introduces new dependency, maybe I should use some other library?

[oberstet]

@CepGamer from the spec (on rawsocket handshake):

The first octet is a magic octet with value "0x7F". This value is
chosen to avoid any possible collision with the first octet of a
valid HTTP request (see here [6] and here [7]). No valid HTTP
request can have "0x7F" as its first octet.

  By using a magic first octet that cannot appear in a regular HTTP
  request, WAMP-over-RawSocket can be run e.g. on the same TCP
  listening port as WAMP-over-WebSocket or WAMP-over-LongPoll.

but only WAMP routers need to make that distinction (if they want to support websocket + rawsocket running on same port) anyway - not clients.

rgd websocket: websocketpp is just fine. I would not use a different lib nor reinvent the wheel.

[Bobface]

So you can not connect to servers with http/wamp mixed protocols? I think in AutobahnJS it works, doesn't it?

[CepGamer]

@Bobface Yes, it works in JS and Python (the ones I checked), but, unfortunately, I may only use C++ in my code.

[oberstet]

As mention, RawSocket has facilities to support running besides WebSocket on one TCP port.

This is not using HTTP upgrade mechanism, and is a router-side feature - there is nothing to implement in WAMP clients.