diff options
| author | Matthias Radestock <matthias@rabbitmq.com> | 2012-10-12 23:31:15 +0100 |
|---|---|---|
| committer | Matthias Radestock <matthias@rabbitmq.com> | 2012-10-12 23:31:15 +0100 |
| commit | 9db422ac20c8b5c995d05b0846a3379049799cd4 (patch) | |
| tree | ce9d873ee27301aa1d0f99d75ca4f333a80cd682 /docs | |
| parent | 913d27ce8ac9af86c1b6f109fb42780bd7f2e9aa (diff) | |
| download | rabbitmq-server-git-9db422ac20c8b5c995d05b0846a3379049799cd4.tar.gz | |
correct essay & comments regarding the 'delayed confirm' rationale
Matthew has confirmed that the "we don't know the msg_seq_no until we
receive the msg from the channel" reason is bogus. The msg_seq_no is
allocated by the channel prior to routing and thus is the same across
the master and all slaves. Hence the 'publish' via gm contains all the
information we need to issue a confirm.
Nevertheless we cannot actually issue the confirm until we've received
the message from the channel. The essay now explains the real reason.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions