-
Notifications
You must be signed in to change notification settings - Fork 70
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
RpcServer serializer is wrong #296
Comments
Hi, @anboo44
To build compatible message serializers, the configuration of message types (the order of message types) must be the same on both the RPC client and the server. |
@eduard-vasinskyi I recognize that Assumed, RpcServer handles types: |
@anboo44 It is not possible to make a client that knows nothing about other message types. |
@eduard-vasinskyi I got it. Thank you so much |
I make a small project to test RPC.
When i set
JoinMsg.class
is first atwithMessageTypes
, messages to my rpcServer are always serialized intoJoinMsg.class
When i set
CalcRpcMessage.class
is first atwithMessageTypes
, messages to my rpcServer are always serialized intoCalcRpcMessage.class
I don't understand why it is.
I want to class types don't care their order in
withMessageTypes
. RpcServer is based on class type that is declared withwithHandler
to serialize message.Please give your advise
The text was updated successfully, but these errors were encountered: