Describe Recommend Way of using Domain Classes and Converters in the manual
How to deal with custom data types, protobuf types, rst etc.
Fragments from the wiki:
Note: more basic explanations of RSB's converters can be found here and here. However, the approaches described there, although seemingly less complex, have some problems, and should not be applied in production code.
Using automatically generated protocol buffer messages for serialization and network communication has several advantages:
- IDL-defined message format (as opposed to an informal "definition" through a particular implementation)
- Proper handling of machine Endianess
- Proper handling of machine word sizes
- Some degree of data validation
- Introspection support
- Generated data-holder classes and (de)serializers
- Available in multiple programming languages without additional effort
- Inter-language consistency of data-holder classes and serialized representations
It may even seem sensible to use the generated protocol buffer message classes as domain classes as well. However, Google's protocol buffer tutorial advises against this (see "Protocol Buffers and O-O Design" in the protocol buffer tutorial).