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] Commented: (AMQP-80) [Global Addressing] Section 3.2: Semantics


    [ http://tools.oasis-open.org/issues/browse/AMQP-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36057#action_36057 ] 

Rafael Schloming commented on AMQP-80:
--------------------------------------

I believe what I was trying to express was something even simpler. Just that "global" doesn't mean global within a given container, but rather truly global. I suggest something like this:

"The domain portion of an AMQP address has global scope. Note that this scope is truly global, not just global within a single AMQP container. This means that provisioning of AMQP addresses must take into consideration not only the container and the local AMQP network, but also the set of transitively connected AMQP networks where a provisioned address may appear."

> [Global Addressing] Section 3.2: Semantics
> ------------------------------------------
>
>                 Key: AMQP-80
>                 URL: http://tools.oasis-open.org/issues/browse/AMQP-80
>             Project: OASIS Advanced Message Queuing Protocol (AMQP) TC
>          Issue Type: Improvement
>          Components: Global Addressing
>    Affects Versions: WD03
>            Reporter: Rob Godfrey
>            Assignee: Rafael Schloming
>
> The last sentence of the first paragraph states:
> "This requires that an AMQP domain MUST be unique among all the addresses that may appear in any of the set of transitively connected AMQP networks where an address might travel."
> What does domain uniqueness *mean*... How is a domain unique within a set of addresses?
> I presume what we are trying to say is somethin like resolution to addresses within a given domain must have the same semantic resolution no matter where in the connected network the message originates from (i.e. there cannot be two endpoints where at on the address /domain/A resolves and /domain/B doesn't ... moreover that /domain/A must resolve to the same logical entity). 

-- 
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]