Alexey Rybalchenko

Ideally it should be a `const TObject &`, or? Then it is clear that the manager maintains the ownership.

A different idea: a `LOG` call should never throw (unless it can't actually log) because of a severity level. It's job is just to make a log entry. The way...

I did a quick test with `LOG(fatal)` at (https://github.com/FairRootGroup/FairRoot/blob/dev/examples/MQ/serialization/data_generator/dataGenerator.cxx#L94) and it throws the exception as expected (which would itself lead to SIGABRT if uncaught). Could you post a stacktrace to...

There is also: ```C++ /**Run over the whole input file with timpe window delta_t as unit (entry)*/ void Run(Double_t delta_t); ``` Although it is a little bit harder to confuse...

Soooo, what are the benefits of going full type here? What do we loose with a simpler: ```cpp namespace fairroot { using EntryID = size_t; } ```

The `MetaHeader` part contains data that will be transferred to a different process, while other members of shmem `Message` class are only valid/meaningful locally per process. ```c++ struct Message {...

I will likely come to this sometime in September.

The need to store the alignment value is for use in Message::SetUsedSize, which may need it in an edge-case. Instead of storing it with each message, we could also accept...

Sounds good, then that could be done when no alignment is provided to SetUsedSize. That way no need to break the interface, alignment argument to SetUsedSize will be optional. Then...

The current state in the dev branch is: - the alignment member is removed. - content of the MetaHeader member is moved directly into Message and sorted: ```c++ Manager& fManager;...