funky-eyes commented on PR #7503: URL: https://github.com/apache/incubator-seata/pull/7503#issuecomment-3041085547
> > make it mutually compatible > > I think it's easier to maintain another package than to maintain compatibility. > > 1. The old package can be deleted at any time > 2. Use the same package and rename it in the future. (If not renamed, the package name is inconsistent with the internal serialization protocol.) I don't think so, because these two things are the same thing, there's no need to distinguish them, and compatibility is not an issue. Fastjson and fastjson2 are differentiated because early fastjson2 had incompatibility problems with fastjson, so they were distinguished. However, fury and fory don't have this problem at all - it's just like io.seata being changed to org.apache.seata. It should maintain backward compatibility. You can have fury directly reference fory's implementation, so both are directly compatible, because whenever fury serialization is called, it will actually use fory serialization. -- 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]
