Hi, just wanted to clarify some concepts regarding the (de)serialization mechanism when using co::Serializable.
The documentation reads: "For serialization, the default co::Object serialization functions are implemented by co::Serializable, which (de-)serializes and resets the dirty bits, and calls serialize or deserialize with the bit mask specifying which data has to be transmitted or received. During a commit or sync, the current dirty bits are given, whereas during object mapping all dirty bits are passed to the serialization methods." What I understand from this is that (get)applyInstanceData is used only during object mapping with passing DIRTY_ALL to (de)serialization and from then on (unpack)pack is used only with the current dirtyBits that are passed to the (de)serialization functions. What I notice though if I run eqPly is that the (de)serialization functions are called for both DIRTY_ALL and with the actual dirtyBits set at each commit/sync. Am I missing something here and if not could I get some more info about the rationale behind this?? Thanks! Petros -- View this message in context: http://software.1713.n2.nabble.com/co-Serializable-get-applyInstanceData-unpack-pack-question-tp7586656.html Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com. _______________________________________________ eq-dev mailing list [email protected] http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev http://www.equalizergraphics.com
