[Enhancement] Refactor eventmesh Rust sdk
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 658
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 52
Description
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/eventmesh/issues?q=is%3Aissue) and found no similar issues.
### Enhancement Request
Due to recent changes in the EventMesh protobuf files, the existing Rust SDK is no longer compatible. Therefore, a refactoring of the Rust SDK is required. The refactoring will be carried out in the following steps:
1. Refactor the gRPC portion of the Rust SDK.
2. Refactor the HTTP portion of the Rust SDK (This work will be done after issue #4481 is completed).
3. Add the TCP protocol to the Rust SDK.
### Describe the solution you'd like
The refactoring will be carried out in the following steps:
1. #4467
2. #4519
3. Refactor the HTTP portion of the Rust SDK.
4. Add the TCP protocol to the Rust SDK.
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) *
Contributor guide
Research direction
Start by reviewing the recent EventMesh protobuf changes and the existing Rust SDK, then inspect issue #4467 for the gRPC refactoring and issue #4519 for the HTTP work. Completion includes a compatible gRPC SDK, the later HTTP refactor, and TCP protocol support, with the HTTP portion waiting on issue #4481.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, rust
- Domain
- api, backend, networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100