I'm already using protocol buffers. The thing is, I can be passing around any protocol buffer serialization; so I need an envelope to tell the receiving party about the type of the message. I'm using multipart messages to pass two protocol buffer serializations; first one that contains data regarding the whole message, the second one, actual payload of the message. I'm happy to hear other approaches to handle this.
cheers Seref On Thu, Jun 2, 2011 at 9:37 AM, Ian Barber <[email protected]> wrote: > On Thu, Jun 2, 2011 at 9:29 AM, Seref Arikan > <[email protected]> wrote: >> >> Thanks Martin, will do that. >> I'm in a bit of a hurry, so I'll try to cut some corners here: any >> alternatives to multipart messages for message envelopes that you'd >> recommend? >> >> Regards >> Seref >> > > Google protocol buffers and json are both popular choices for stuffing > multiple bits of data together. > > Ian > > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
