You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 15, 2018. It is now read-only.
Hi, let me suggest to implement the native binary support, so Erlang will shine and be able to receive many thousands of connections without the hard job of dealing with message conversion for every message. http://bert-rpc.org/
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion,
Which connection are you thinking of?
Websocket we could just introduce another kind of encoding like wamp-bert.
Over TCP we should talk to Travendo so a bit gets reserved inside the TCP-Handshake for the protocol.
Anyway it looks very good and I am going to implement it.
Would you mind telling me what you are using it for, I am very interested in the use cases of Erwa.
The new supported serialization is internally called
erlbin and raw_erlbin. This also a fix for issue #12 .
all messages will be converted to binary and back using
the erlang functions term_to_binary() and binary_to_term().
It is not offically in the spec, yet you can enable it by setting the application env 'erlbin_number' for the raw transport.
For an example see test/roundtrip_SUITE.erl (init_per_suite/1 and pubsub_tcp/1).
Hi, let me suggest to implement the native binary support, so Erlang will shine and be able to receive many thousands of connections without the hard job of dealing with message conversion for every message. http://bert-rpc.org/
The text was updated successfully, but these errors were encountered: