WebSocket request-response subprotocol -
websocket provide bi-directional communication human being talks. client can send data server , server can send data client @ anytime. question ? request-response behavior ? client ask server , wait response. seems websocket doesn't provide link client data (request) server data (response).
it's work of subprotocol , have ideas on how (send id request , wait reponse same id until timeout period).
in order not remake wheel , save time, looked on internet existing solution haven't found related (maybe bad keywords).
so there aware kind of work or missing ?
the websocket application messaging protocol (wamp) http://wamp.ws/ provides rpc (remote procedure call) , pubsub (publish & subscribe) messaging patterns on top of raw websocket purpose.
wamp proper websocket subprotocol, uses websocket transport , json payload format. rpc implemented using 3 messages, , messages contain "call id" correlate asynchronous rpc server responses client initiated procedure calls.
disclaimer: author of wamp , (open-source) wamp implementations. open initiative, others started on boat. ultimately, there should wamp rfc defining protocol .. still in stages.
Comments
Post a Comment