On 9/19/2012 6:30 PM, Michael Haberler wrote: > -- when the time has come to send a status update message, go through the > member list, pull current values, and create a status message (this would > have to call upon the serialisation method employed in the future, for > instance Google protocol buffers, or JSON, or whatever we decide on)
Two great quotes from the 0mq FAQ: > Some middleware products do provide their own serialization API. We > believe that doing so leads to bloated wire-level specifications > likeCORBA <http://www.omg.org/docs/formal/04-03-12.pdf>(1055 pages). Having lived through CORBA hell with in-house projects, I couldn't agree more. > Note that serialization implementations might not be as performant as > you might expect. You may need to benchmark your workloads with > several serialization formats and libraries in order to understand > performance and which format/implementation is best for your use case > (ease of development must also be considered). I only know JSON, and that not so well. Is there some simple but relevant benchmark that could be cobbled up to explore it vs the rest of the contenders? Regards, Kent ------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
