Skip to content
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

Auto-acking support #199

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Auto-acking support #199

wants to merge 1 commit into from

Conversation

bergie
Copy link
Member

@bergie bergie commented Jun 13, 2017

This makes it possible to use noflo-runtime-msgflo for participants that don't produce output corresponding to received packets. For example, web servers that receive results from some background worker.

@bergie bergie requested a review from jonnor June 13, 2017 07:33
@jonnor
Copy link
Member

jonnor commented Jun 13, 2017

I'm not so keen on this option. ACK'ing is a key aspect of MsgFlo use, and I think one understand and use it. If someone really does not want to ACK properly, they can just send the input to an exported outport (via a core/RepeatAsync or similar).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants