[zeromq-dev] multipart message receiving does not work with C++

[Seref Arikan]

Hi Martin,
Indeed this would be a solution, and Jashua has kindly provided a link
for a way to do this. I'm using protocol buffers in a complicated
wrapper scenario, and in general I'd like to get multipart messaging
up and running, since it feels as if it will offer more flexibility.
Given my current setup, multipart messages is method that offers
shorter time to functionality required.

Any reason I should avoid multipart messages? Performance? Stability?

On Thu, Jun 2, 2011 at 11:53 AM, Martin Sustrik <sustrik at 250bpm.com> wrote:
> On 06/02/2011 11:37 AM, Seref Arikan wrote:
>>
>> 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.
>
> Why not simply serialise both envelope and data using protocol buffers?
>
> Martin
>
>