Rationale: The serialization inside message-io was merely a shortcut and in most cases, it reduces the power of the user by saving 2-3 lines of their code. The serialization should be handle by the user for several reasons:
The user could want to decide to send the message base on the serialized data size.
(e.g. choosing a different transport if the serialized size exceeds the max packet size)
The user could want to perform some action over raw data.
The user could make a gateway without needed to deserialize to serialize again.
The user could want specific serializing methods.
The user could mix several kinds of serializations.
Or simply, there is no need to serialize in some cases.
Rationale: The serialization inside
message-iowas merely a shortcut and in most cases, it reduces the power of the user by saving 2-3 lines of their code. The serialization should be handle by the user for several reasons:Also it PR brings other minor changes:
remove_resourcebyremoveAdapterEventNetwork::split_and_map().encodingmodule.