-
-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
customize user data serialization for request and response #65
Comments
To customize serialization you can register your custom implementation of the interface It will replace the default implementation Please notice that currently this will impact all IPC endpoints. |
It is not so easy, since Google Protobuf requires objects to be generated from the pseudo code (for example) so Additionally I'd like to get some binary serialization rather then using json or xml |
I see the issue now. I'll see if I can make serialization customization easier in next version. |
Sorry due to lack of time I'm again moving this issue to next milestone |
Hello
I'm looking for wcf replacement in the .netCore. REST is fine but is too slow when complex data types are being serialized.
It would be nice to have possibility to replace user data JSON serialization with custom one. It can be useful if Protobuf or another framework is used with improved serialization algorithms.
My initial idea was to serialize
IpcRequest.Parameters
andIpcResponse.Data
as byte array and then callDefaultIpcMessageSerializer
However the problem is that not every type is serialized to binary so certain header has to be used to deserialize request\response data properly back to object.
For example, new interface like
IIpcMessageDataSerializer
can be introduced.It can be used by
IpcReader
andIpcWriter
to serialize method parameter and|or result value.Here is
IpcWriter
class draft to explain it betterAnd adjust
IpcReader
as belowThe text was updated successfully, but these errors were encountered: