Skip to content

Conversation

@jfontan
Copy link
Contributor

@jfontan jfontan commented Oct 3, 2018

This adds the possibility to create memory queues that do not block when the queue EOFs. This mimics the behavior before #13 that is expected by other projects.

This adds the possibility to create memory queues that do not block when the queue EOFs. This mimics the behavior before src-d#13 that is expected by other projects. Signed-off-by: Javi Fontan <jfontan@gmail.com>
@jfontan jfontan requested review from a team and carlosms October 3, 2018 10:33
@kuba--
Copy link

kuba-- commented Oct 3, 2018

Personally, I would consider use channels here or pass context with cancel to consumer (Next).
Because when you want to stop consuming it's kind of special case of EOF.
So either you can close the channel or cancel context.

@jfontan
Copy link
Contributor Author

jfontan commented Oct 3, 2018

I would also use a channel here. In fact the AMQP version uses a channel behind the scenes. The problem is that there's software already using this interface (rovers, borges and lookout).

Copy link
Contributor

@carlosms carlosms left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@jfontan jfontan merged commit 6214d25 into src-d:master Oct 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

5 participants