-
Notifications
You must be signed in to change notification settings - Fork 169
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 streams to push consumers #527
Conversation
} | ||
|
||
impl futures::Stream for Stream { | ||
type Item = 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.
Result<Message, Error>
? that would mean tracking publish attempts in response to flow control etc
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 think that this can be answered as we discussed at client sync: we're aiming to report on any errors on specific consumers/subscriptions instead of silently passing by them or reporting them on registered callback.
So, Result<Message, Error>
sounds better.
For sure we need that for Pull, and handling those errors differently (i.e. callback on Consumer) would make pretty inconsistent API for no good reason.
} | ||
|
||
impl futures::Stream for Stream { | ||
type Item = 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 think that this can be answered as we discussed at client sync: we're aiming to report on any errors on specific consumers/subscriptions instead of silently passing by them or reporting them on registered callback.
So, Result<Message, Error>
sounds better.
For sure we need that for Pull, and handling those errors differently (i.e. callback on Consumer) would make pretty inconsistent API for no good reason.
continue; | ||
} | ||
Some(_) => { | ||
continue; |
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.
are we sure that there are no other statuses we have to handle in any way? :)
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.
Fairly sure, should be at parity with sync at-least.
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.
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!
No description provided.