FinalT opened a new issue, #2565: URL: https://github.com/apache/dubbo-go/issues/2565
**Why is this needed**: This issue was brought up by #2539. Although the export logic of the server layer was separated, the generated triple files still depend on the server layer. This means that our internal service module still depends on the server layer, and our underlying modules depend on these internal services. As the server layer is an upper-level module, it depends on these lower-level modules, resulting in a circular dependency. **What would you like to be added**: However, the underlying modules typically only use a few interfaces of the internal services, and the number of internal services is not large. It is not necessary to depend on all packages of the internal services. One possible solution is to create an "internal" package as the top-level module, where the service methods are defined. Then, the internal services can still be registered through the server layer, and the methods can be further registered in the "internal" package. This way, other modules do not need to directly depend on the internal services. Refer to grpc-go to resolve circular dependencies -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
