[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: AMQP Addressing Questions
In reference to the AMQP Addressing Spec. v1.0 (wd01): ===== In the opening paragraph of section 3 (Addresses), the fields in which addresses have formal meaning are listed ({target,source}.address, to). Shouldn't the reply-to field of the message properties be listed here as well? ===== Section 4.5 (Dynamic Routes) - I've read this a dozen times and I still don't know what the intent is. What is meant by "advertise"? When "source or target" is mentioned, does this refer to local and or remote termini? Is this simply a way of saying that a receiver may "register" its address with the peer? ===== Section 6.5 (Request/Response) - This needs some work. The issue here really comes down to:
I further claim that in the simple point-to-point case (no intermediary), the fact that the server assigns the reply-to addresses for its clients does _not_ constitute broker functionality and does not involve the creation of a temporary queue. I'm sure that my above claims will be debated. However, if we agree that they have merit, we need a mechanism by which to convey the information from access-node/server to client. The link-attach command has a "dynamic" field that can be used to signal that the target of an outgoing link needs to be assigned by the sending terminus. This would allow a client to create a listening link to "dynamic" and wait for the peer to set the target address in the returning attach frame. This address could then be used as a reply-to for any requests sent to the same container. Thoughts? Regards, -Ted |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]