jock

socket for jaem

highlights

1. minimal (around 500 loc)
2. no dependency (yes, we have our own http and websocket implementation)
3. simple (provide everything needed to make the ubf over websocket, nothing else, for full http and websocket implementation, please check cowboy
4. ubf only, no alternative
5. enable bidirectional function call between beam and jaem (use case: write common-test in erlang for javascript code on jaem)

purpose

provide a duplex socket connection between beam and jaem

motivation

ad-hoc protocol is unessarily complicated and painful to implement and work with. Joe who has sympathy for us bring ubf from heaven to earth. we decide not only implment it, but also build into the core of our architecture.

reference

source