On 08/18/2011 07:55 AM, Toralf Lund wrote:
Gordon Sim wrote:
A 'link' is the logical association between a sender or receiver and
their target or source respectively. It a pathway along which messages
travel to or from some 'node'.
>
Well, yes, that's what I've read, and I understand all the words, but I
have no idea of what it really means... Perhaps the problem is that
talking about "links" and "nodes" is completely misplaced in the context
of AMQP, IMO. To me a link between nodes is something like a direct
socket connection between applications running on two different
computers, which is precisely what I'm trying to avoid by using AMQP.
But that's a different discussion, of course... (And I know, the terms
are from the AMQP crowd, not QPid developers.)
I think of a node as a rendezvous point through which producers and
consumers of messages coordinate. A link is then just the relationship
of my application process with that rendezvous, i.e. the desire to
publish or consume messages.
If a subscription is the desire to receive messages, there is an
analogous concept for publishing, i.e. a desire to send messages. I
don't know of any good term for that (a 'pubscription' perhaps :-), but
'link' is supposed to cover both of them. It is not intended to be tied
to any low level socket notions, merely a way to refer to inflows and
outflows of messages from my application process.
At least that's how I see it...
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
