Agreed. If you have rock-solid Google's Protocol Buffers
implementations on both ends, their schema formalism works for you, and
you don't mind the protocol being harder for a programmer to eyeball in
most tools than sexp/JSON, then (the unfortunately-named :) Protocol
Buffers is a great option.
Or, you could keep Protocol Buffers as a backup or future option, while
you start rapidly with something else. Rapid start might be as simple,
yet perhaps perfectly viable, as this:
(write `#(my-message-opcode ,x ,y ,z) my-tcp-socket-output-port)
--
You received this message because you are subscribed to the Google Groups "Racket
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
