-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
GRPC endpoint clean up. Add missing protocol in doc #5428
Conversation
@@ -61,7 +61,7 @@ | |||
|
|||
#define REGISTER_GRPC_INFER_THREAD_COUNT 2 | |||
|
|||
namespace triton { namespace server { | |||
namespace triton { namespace server { namespace grpc { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice job cleaning this code up!
What is the purpose/benefit of the grpc namespace? I don't see where it's changing anything beyond requiring the addition of "::" before each grpc namespacing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I missed the part of dropping GRPC prefix from the objects, but the idea is to group correlated objects in the form of namespacing. Otherwise, we need to do the grouping via prefixing. If you look across all endpoints, you will see that all endpoint live under triton::server namespace, and to distinguish the names, there is prefix with the endpoint types (i.e. HttpXXX
, GrpcXXX
).
Another thing is that if you are modifying within GRPC endpoint, you can refer to objects without the mention of "GRPC", the endpoint type is implied in this context.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it, that makes sense. Thanks for explaining the reasoning!
Will leave this conversation up in case it's helpful for anyone else.
This is still pending. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice refactoring 🎉
No description provided.