[openscreenprotocol] Why a custom binary control protocol?

rektide has just created a new issue for https://github.com/webscreens/openscreenprotocol:

== Why a custom binary control protocol? ==
Hey all. Very glad to see this spec in progress. I wasn't aware of ya'll till recently. Overall very promising work!

I'm very curious, confused, & frankly a small bit concerned about your choice to implement a custom binary protocol for the control protocol. What are the justifications for writing your own message encoding protocols?

Generally I'd expect a more extensible, developer-friendly, well known messaging format to be put into service, as opposed to rolling all your own binary messages. Sending JSON messages (protocol framed, or newline delimited if need ), for example, would be the bread & butter answer, using existing, very common technology so as to keep folks from having to implement your custom messaging system. It would also be more readily extensible, for future versions of the protocol to grow on top of.

Thanks all. Best of luck! I'm so excited for this future!

Please view or discuss this issue at https://github.com/webscreens/openscreenprotocol/issues/86 using your GitHub account

Received on Thursday, 10 May 2018 21:19:14 UTC