#1 Streamline MessageImpl

[Jim Alateras]

MessageImpl is composed of many fine-grained objects
such as MessageId, Timestamp, Priority etc, which add
to the streaming overhead. Since a message may be
serialized many times during its lifetime it is important
to minimize this overhead.

The proposal is to remove the fine-grained objects and to
make the MessageImpl implementation more compact
and efficient.

The other option is to always compress the body before
sending the message to the server.

[Tim Anderson]

Logged In: YES
user_id=557161

. Large messages could also be transmitted and stored
chunked to avoid serialization overhead. The prototype
io layer packetizes messages but is still required to
cache and re-assemble the message at the receiver.

. message headers should be stored separately to
message bodies. This can be used avoid destreaming
entire messages from the database when using
selectors.