You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@seata.apache.org by "funky-eyes (via GitHub)" <gi...@apache.org> on 2025/07/06 13:13:43 UTC

Re: [PR] feature: support fory serializer and fory undolog parser [incubator-seata]

funky-eyes commented on PR #7503:
URL: https://github.com/apache/incubator-seata/pull/7503#issuecomment-3041480982

   > > I don't think so, because these two things are the same thing
   > 
   > If I follow your idea, I will first load org.apache.fory.Fory, and if successful, run it according to Fory. If the class cannot be found, try to load org.apache.fury.Fury.
   > 
   > No more new modules, still in the original modules `seata-serializer-fury`.
   > 
   > Is this OK?
   > 
   > 
   
   I don't think this is necessary, because fory is just fury. As long as there's no fory dependency, just prompt the user to upgrade the dependency to fory, and describe the upgrade from fury to fory in the changelog so users can switch dependencies.


-- 
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: notifications-unsubscribe@seata.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@seata.apache.org
For additional commands, e-mail: notifications-help@seata.apache.org