-
Notifications
You must be signed in to change notification settings - Fork 68
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
Initial version of test.proto #13
Conversation
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.
Just a couple of small comments.
test/test.proto
Outdated
// This gNOI service is a collection of operational RPC's that allow for the | ||
// testing of a target by triggering events that otherwise would be difficult | ||
// to trigger without sophisticated test-bed. | ||
service StepExecutionService { |
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.
Lets have only one service in this file which targets testing. So please pick a generic name like "Test" or something. This name is a bit non generic.
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.
OK
test/test.proto
Outdated
// messages. Execution of each step is confirmed by transmitting back a | ||
// StepExecutionResult message. | ||
rpc ExecuteSteps(stream StepExecutionRequest) | ||
returns (stream StepExecutionResult); |
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.
Please use the format
rpc Foo (stream FooRequest) return (stream FooResponse)
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.
OK
test/test.proto
Outdated
// ExecuteSteps executes steps specified in the stream of StepExecutionRequest | ||
// messages. Execution of each step is confirmed by transmitting back a | ||
// StepExecutionResult message. | ||
rpc ExecuteSteps(stream StepExecutionRequest) |
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.
Why not just call this Execute and messages ExecuteRequet and ExecuteResponse? Seems more generic.
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.
OK
No description provided.