-
Notifications
You must be signed in to change notification settings - Fork 642
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Enhancement] Java sdk split multiple sdk by communication protocol #1013
Comments
Welcome to the Apache EventMesh (incubating) community!! Please make sure to include all the relevant context. If you are interested in contributing to our project, please let us know! Want to get closer to the community? Mailing Lists:
|
@Pil0tXia Is it still necessary to implement this issue in the current version? If there is one, I would like to give it a try. |
@qqeasonchen @mytang0 Is it still necessary to implement this issue in the current version? If there is one, I would like to give it a try. |
In #4759 , we do not think this is the best time to do, I will close it now, we will reopen it until we think it is necessary to do this, thank you for you suggestions. |
I get that. But in this issue, i found that the EventMeshCommon class in the original TCP package was referenced by the classes of grpc, HTTP, and other modules. So should I placed this class under the Common module and corrected the reference? This also eliminates the coupling between the modules of the Java SDK. |
Search before asking
Enhancement Request
Java sdk split multiple sdk by communication protocol, implement the slimming of the java sdk.
Describe the solution you'd like
Java sdk split multiple sdk by communication protocol.
Are you willing to submit PR?
The text was updated successfully, but these errors were encountered: