[zeromq-dev] RE : How to send/receive a custom C++ object via zeromq sockets?

[Michi Henning]

I've been working with Cap'n Proto the past two weeks, and I have to say I'm impressed.

Very fast, and a nice and easy-to-use API. Well worth a look!

Michi.


On 18/09/2013, at 16:13 , DEBROUX Lionel <lionel.debroux at atos.net> wrote:

>> I strongly recommend Google's Protocol Buffer as the
>> serialization/deserialization tool. It's fast, convenient and robust.
>> It directly transform an object to the bytes formation (and
>> vice-versa), so can be send/recv through zeromq sockets. We are
>> using it in our online game, and it works well so far.
> I second Michael's recommendation, the Protocol Buffers spec and
> implementations for many languages are great. The integration with
> other Google tools, such as Snappy, is obviously good as well.
> 
> For simple data types, MessagePack is simpler and more efficient than
> Protocol Buffers, and has implementations for many languages as well.
> However, Protocol Buffers clearly offers more features, even in "lite"
> mode.
> Therefore, the choice boils down to your current and future needs :)
> 
> 
> Lionel.
> ________________________________
> 
> 
> Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos ne pourra être engagée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être engagée pour tout dommage résultant d'un virus transmis.
> 
> This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>