Sounds simple - but I couldn't get my head around the delegates and expressions used to create the objects to an extent where I could create a pooling system for the deserialized objects.

My only worry about using MessagePack or almost any serialization is the fact that I am going to be using MessagePack on my server and client (intended use - I believe) I'm going to be deserializing a lot of messages and I could manually cleanup the objects but I have a feeling pooling the objects would be more efficient.

Any thoughts on this?

Could the deserialization be extended and customized so that I can pool the objects?

I saw that you have an attribute for constructors but I didn't see it referenced anywhere on the repo.