I am writing to provide you with the minutes from our community meeting
held on December 12, 2023.
The meeting was productive, and we covered
several  topics and conclusion as outlined below:

Moderator: Minghua Xie

*Attendees*   Minghua Xie,Yixiayixia,Junmin Jiang,Chen Jianbin,Min 
Ji,Zhongxiang Wang,  QiuFeng Liu totaling 7 people.


*Discussion items:*


1. Multi-version/multi-protocol compatible transformation phase
- Phase 1: TC supports compatible with v0 (<0.7.1) version client 
communication(in progress).
- Phase 2: TC supports recognize different versions of protocols >v1 and 
processing(in progress).
- Phase 3: TC supports compatible with different protocol communications (e.g. 
grpc, todo)

2. Progress of multi-version protocol functionality
- TC supports compatible with v0 (<0.7.1) version client communication #5738 : 
Main process writing completed, to be split up
- TC supports recognize different versions of protocols >v1 and handle #5738: 
Main process writing completed, to be split up
- mock-server#5738: main process completed, to be optimized and  split up

3. Pull-request splitting of multi-version protocol related functions (all 
completed functions)
- mock-server: separate pr
- Public functions (e.g. SeataSerializer supports version recognition): split 
pr on demand.
- Compatible with v0 protocols: separate pr (mock-server improve the test cases 
before considering merge)
- Multi-version protocol support > v1: separate pr (mock-server improve the 
test cases before considering merge)

4. mock-server optimization direction
- Mock process and methods: research zookeeper and other middleware
- Test module division: mock-server separate sub-module, the current version of 
the test moved to seata-test, v0-related content moved to seata-samples 
repository
- Mock scenarios to improve coverage: focus on asynchronous scenarios (such as 
transaction timeout),refer to the implementation of the seata-samples


5. server-client version negotiation capabilities
- Refer to the nacos summer code implementation

Reply via email to