-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add support for cursors to LookupResources #57
Conversation
@@ -76,6 +76,15 @@ message ZedToken { | |||
} ]; | |||
} | |||
|
|||
// Cursor is used to provide resumption of listing between calls to APIs | |||
// such as LookupResources. | |||
message Cursor { |
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.
Do we need a message for this or should we just use a string field in the parent message?
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 like having a message in case we need to make semantics changes to it, like we do for ZedToken
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 guess that's fine since clients will just copying this whole message at a time if they need it.
If they maybe wanted to save it in a db or something, it could help to already just be a string.
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.
Yeah, that's the idea
// before the stream is closed on the server side. By default, the stream will continue | ||
// resolving resources until exhausted or the stream is closed due to the client or a | ||
// network issue. | ||
uint32 optional_limit = 6; |
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.
Can we set a max here too?
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.
Sure
Updated |
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.
LGTM
Remains backwards compatible because the new fields are optional on the request