Changes between Version 5 and Version 6 of Documentation/Serialization

Timestamp:

Feb 4, 2010, 6:43:27 PM (15 years ago)

Author:

Christoph Mayer

Comment:

--

Documentation/Serialization

@@ -96 +96 @@
 }}}
 
+The code which is between {{{sznBeginDefault}}} and {{{sznEnd}}} is called for serialization and for deserialization. Sometimes it is necessary to distinguish between the two for special handling. Therefore, you can use the functions
+{{{
+#!cpp
+X.isSerializer()
+X.isDeserializer()
+}}}
 
+When you want to have several message classes, you require one contained class where to can store which inner class is carried. This is, because messages don't carry there type with them. This means you always must know what kind of message you are delivered. Therefore, make a container class where you store the specific type stored. Make sure that your base class serializer always triggers serialization of the encapsulated class through
+{{{
+#!cpp
+X && Payload();
+}}}
 
-
-if (X.isDeserializer())
+You will find the following code in the !PingPong sample that shows how to convert the incoming message to your format and invoke the deserializer:
+{{{
+void PingPong::onMessage(const DataMessage& msg, const NodeID& remote, const LinkID& lnk) {
+    PingPongMessage* pingmsg = msg.getMessage()->convert<PingPongMessage> ();
+    ...
+}       
+}}}