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] (AMQP-112) detail behaviour when addressed node doesn't exist etc


    [ https://issues.oasis-open.org/browse/AMQP-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=65777#comment-65777 ] 

Rob Godfrey commented on AMQP-112:
----------------------------------

This is a fair point :-)

What do we want to say, that if the source supports the rejected outcome then the disposition of the transfer will be "rejected" and the error carried by the rejected disposition will be the error that would have been carried by the link detach (e.g. not-found the supplied address does not resolve to an address).  

If the source does not support the rejected outcome then the link will be detached with the error that would have occurred upon attempting to establish a link to the address.  In this case the info map of the error on the detach SHOULD additionally contain the key "delivery-id" with the value being an unsigned integer (delivery-number)?

> detail behaviour when addressed node doesn't exist etc
> ------------------------------------------------------
>
>                 Key: AMQP-112
>                 URL: https://issues.oasis-open.org/browse/AMQP-112
>             Project: OASIS Advanced Message Queuing Protocol (AMQP) TC
>          Issue Type: Bug
>          Components: Anonymous Terminus
>    Affects Versions: anonterm-WD1
>            Reporter: Robert Gemmell
>
> # 2.2 Routing Nodes
> The section describes that messages will be "forwarded to the node referenced in the to field of properties of the message just as if a direct link has been established to that node". 
> Should it also detail anything here around behaviour for when e.g the node doesn't exist, or the sender isn't authorized to send there, etc, which will be slightly different than if a direct link had been attempted? It seems odd to cover related behaviour later in '2.2.1 Link Properties And Target Capabilities' without having done so.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


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