Use a standard messaging format / protocol - Githubissues

jonkirkman / tronhub

Server to coordinate awesome light-cycle battles between remote clients

MIT License

3 stars 1 forks source link

Use a standard messaging format / protocol #3

Open jonkirkman opened 9 years ago

jonkirkman commented 9 years ago

How should messages between the client and server be formatted? The format should be framework agnostic and well supported across many languages.

Some such formats / protocols:

Stomp http://stomp.github.io/ http://jmesnil.net/stomp-websocket/doc/
WAMP (Web Application Messaging Protocol) http://wamp.ws/
~~Protobuf https://developers.google.com/protocol-buffers/~~ (actually a serialization format rather than a messaging format)
Socket.io-protocoli https://github.com/automattic/socket.io-protocol

billmccord commented 9 years ago

Highly recommend you look at SockJS also: Socket.io vs SockJS http://www.quora.com/Sock-js/What-are-the-pros-and-cons-of-socket-io-vs-sockjs http://xsnippet.org/359042/ https://groups.google.com/forum/#!topic/sockjs/lgzxVnlth54

And although this was written for Python, there is some very good discussions and design patterns for doing real-time apps. Worth reading: http://mrjoes.github.io/2013/06/21/python-realtime.html