-
Notifications
You must be signed in to change notification settings - Fork 3
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
custom serialization #4
Comments
The main reason is that, you need to generate encoding/decoding for client stub for that serialize format. Currently I only write for JavaScript. Currently |
Then you need to generate client stub for that format. I welcome any suggestions for improving our data standardization, Feel free to share any idea to improve current encoding strategy. |
hi, just found that databuf doesn't useful for long-term systems/api, there's no support for deprecating/reserving fields as it done in protobuf serialization protocol, so, u can easily get messed with api versioning i'm talking about
|
Yes, Currently this API is not yet supported: #[repr(u16)]
enum Action {
Noop = 1,
Add { x: i32, y: i32 } = 2,
Print(String) = 3,
} An object can be represent using |
hi, seems that
frpc
strictly bounded bydatabuf.rs
, but what if we want to use other serialization system. like a bebop, bincode2 or smth like that?The text was updated successfully, but these errors were encountered: