We reached a consensus at the weekly meeting. Firstly, we need to ensure that its license complies with Apache standards. Following that, we plan to conduct performance comparisons with Seata's existing serialization methods and the corresponding serialized classes. We expect to provide further updates and reports at the next weekly meeting. Thank you for your attention to this feature.
Jianbin Chen, githubId: funky-eyes Jiangke Wu <xingfude...@apache.org> 于 2024年8月4日周日 17:52写道： > Sounds good. Look forward to further discussion. > > > > Best Regards, > Jiangke Wu(xingfudeshi) > > > On Mon, Jul 29, 2024 at 15:34 Jianbin Chen <jian...@apache.org> wrote: > > > Hi Seata Community, > > > > I have an idea. Through the Apache Community Overcode Asia conference and > > my daily attention to open source, I learned about an excellent open > source > > project, Apache Fury, which is a project that has recently entered the > > Apache Incubator. After communicating with its members, I learned that it > > is a high-performance serialization tool with a white list, long-term > > maintenance, and no current security vulnerabilities. I hope that when > some > > unmaintained serialization tools or tools with low security are phased > out > > in the future, there will be corresponding supplements, such as hessian2 > > and fastjson. Their corresponding supplements may be fury and fastjson2. > So > > I hope that in the 2.2 milestone, we can add a feature to add support for > > Apache Fury for undo log serialization and communication protocol > > serialization. This will also increase our interaction with excellent > > components under the Apache organization. Welcome everyone to communicate > > and exchange with me on this proposal. > > > > Best regards, > > > > Jianbin Chen, githubId: funky-eyes > > >
