chaokunyang commented on issue #2923: URL: https://github.com/apache/fory/issues/2923#issuecomment-3586170192
@ankyhe You may need to include a version header and bundle two versions of Fory during upgrades so the system can choose the correct version for deserialization. This avoids compatibility issues when one service is updated before the other. We understand that binary compatibility is important. Full binary compatibility will be guaranteed starting from Fory 1.0. Before that, some breaking changes are still possible, even in minor version updates, because 0.x.x versions are not yet considered stable. We will still try to minimize such changes. For Fory Java specifically, we have only a few tasks left before binary compatibility is fully stabilized: 1. Remove the key/value–based CompatibleSerializer and use the meta‑shared CompatibleSerializer for all serialization. 2. Make ObjectStreamSerializer use the meta‑shared CompatibleSerializer for every layer in the object inheritance chain. 3. Reserve 256 class IDs for Fory’s internal registry so user‑defined class IDs start from 0, with Fory adding 256 internally. Once these are done, Java serialization will be stable at the binary level, and we will move toward the Fory 1.0 release. That said, in most real‑world scenarios you do not need to upgrade Fory frequently. The current version is already feature‑complete enough for typical use cases. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
