delta/rabbitmq-server.git, branch bug25225

merge slave 'confirm' decision making and action

2012-10-15T16:34:43+00:00

similar to what we did in rabbit_amqqueue_process

refactor: handle all msg statuses uniformly

2012-10-15T15:29:48+00:00

refactor: deal with 'publish' and 'publish_delivered' in separate clauses

2012-10-15T15:25:34+00:00

refactor: extract commonality between 'publish' and 'discard'

2012-10-15T15:13:50+00:00

deal with confirms in slave 'discard'

2012-10-15T14:07:28+00:00

merge default into bug25225

2012-10-15T12:00:17+00:00

Merge bug25226

2012-10-15T11:16:13+00:00

plug leak

2012-10-13T07:44:47+00:00

always remove from PendingCh when we receive a msg via gm that we
previously received from the channel.

merge default into bug25225

2012-10-12T22:42:06+00:00

correct essay & comments regarding the 'delayed confirm' rationale

2012-10-12T22:31:15+00:00

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.