Producer flow control commented on by Aidan Skinner (Jun 27, 2008).

Comment:

Policies will essentially be high water marks, applied onto queues, routing keys or exchanges.

We don't need to record all the sessions that have published, just the ones that have been flowed, which should be cheaper. Recording the list of all sessions that have published could unnecessarily flow some producers that weren't going to publish again, but I guess that's also a risk with doing it once they've published-while-delinquent and is probably more in line with user expectations.

The reason that they get flowed after the delinquent publish is to deal with the async publish.

Reply via email to