[Enhancement] Unify protocol port configuration refactoring
- 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
1、Unify tcp/grpc/http protocol port
2、Make protocol port and type configurable
### Describe the solution you'd like
eventMesh.server.protocol.unified.port=10000
eventMesh.server.protocol.http.enabled=true
eventMesh.server.protocol.grpc.enabled=true
eventMesh.server.protocol.tcp.enabled=true
### 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
The issue names no files, tests, or entry points. Start by locating the TCP, gRPC, and HTTP server configuration and startup code, then trace how their ports and enabled states are currently defined. Done means the three protocols use the requested unified port configuration and can be enabled or disabled through the listed settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, java
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100