Auto-acking support - Githubissues

noflo / noflo-runtime-msgflo

NoFlo runtime for AMQP/MQTT

10 stars 8 forks source link

Auto-acking support #199

Open bergie opened 7 years ago

bergie commented 7 years ago

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.

jonnor commented 7 years ago

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).