Skip to content
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

[Java] Meta shared mode serialization #80

Closed
chaokunyang opened this issue May 6, 2023 · 0 comments · Fixed by #225
Closed

[Java] Meta shared mode serialization #80

chaokunyang opened this issue May 6, 2023 · 0 comments · Fixed by #225
Labels

Comments

@chaokunyang
Copy link
Collaborator

chaokunyang commented May 6, 2023

Is your feature request related to a problem? Please describe.
For class forward/backward compatibility, fury needs to send class meta to peer everytime, which is time-consuming, and consume more bandwidth.

Describe the solution you'd like
If the serialization sender and receiver are serialized serially in a certain context (TCP connection), then some metadata (class name, field name, final field type information, etc.) can be shared between multiple requests in that context. These type information will be sent to the other end during the first serialization in that context. This way, the other end can rebuild the same deserializer based on the type information, so that it can still deserialize correctly when the fields on the serialization and deserialization sides are inconsistent. At the same time, unnecessary metadata serialization overhead can be reduced in subsequent serialization.

Additional context
#197

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant