You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is it possible to use this framework but not use the default MsgPack object serialization?
I use the MsgPack c# bindings but use for all objects a customer serializer. But when I use the DynamicProxy for example, the framework would use the default MsgPack serialization.
So there some API to pass byte[] and only take advantage of the communication features?
Thanks!
The text was updated successfully, but these errors were encountered:
is it possible to use this framework but not use the default MsgPack
object serialization?
I use the MsgPack c# bindings but use for all objects a customer
serializer. But when I use the DynamicProxy for example, the framework
would use the default MsgPack serialization.
So there some API to pass byte[] and only take advantage of the
communication features?
Thanks!
—
Reply to this email directly or view it on GitHub #1.
Hi,
is it possible to use this framework but not use the default MsgPack object serialization?
I use the MsgPack c# bindings but use for all objects a customer serializer. But when I use the DynamicProxy for example, the framework would use the default MsgPack serialization.
So there some API to pass byte[] and only take advantage of the communication features?
Thanks!
The text was updated successfully, but these errors were encountered: