OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

amqp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Created: (AMQP-39) Clarify settlement on multi-transfer deliveries

Clarify settlement on multi-transfer deliveries

                 Key: AMQP-39
                 URL: http://tools.oasis-open.org/issues/browse/AMQP-39
             Project: OASIS Advanced Message Queuing Protocol (AMQP) TC
          Issue Type: Improvement
            Reporter: David Ingham
            Assignee: Rafael Schloming
            Priority: Minor

From Steve Huston's comments:

Part 2, section 7.5, delivery-id: How would one know if a message with
delivery-id(2) is a mis-id'd continuation of delivery-id(1) or a new
message? By using the delivery-tag as well (if it's missing, it must be a

Part 2, section 7.5, settled: What is the desired/required behavior if the
values in different transfers of a multi-transfer message are different?

RS: We should make it clear that settlement in general is idempotent, i.e. things can go from unsettled to settled, but not from settled to unsettled. Probably in 2.6.12 where we first talk about settlement.

RG: Should also add text to other fields (e.g. delivery-tag, message-format) defining that they cannot change between transfer frames on the same delivery (though they may be omitted).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]