experimental: wamp.2.capnproto.split_payload

[om26er]

• first byte WAMP message type (int)
• next two bytes contain length of the WAMP message (without payload i.e. no args or kwargs)
• next three bytes contain length of the payload
• next two bytes are zeros (for future extensibility)
• next follows the message itself
• next follows the message payload (args, kwargs)

So essentially when running on top of unix socket.

Supporting this over websocket is fine but mainly we want to target that for unix socket / tcp socket -- i.e. when using rawsocket transport on the same host.

Here is a list of messages with payloads

1. call
2. invocation
3. yield
4. result
5. publish
6. event
7. error