From fcd7c8ddc2f0231881d1fc22b8cefe6bb4753dc5 Mon Sep 17 00:00:00 2001 From: Jonathan Robie Date: Thu, 22 Apr 2010 13:28:33 +0000 Subject: Applied new patch from Gordon. git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@936838 13f79535-47bb-0310-9956-ffa450edef68 --- qpid/doc/book/src/High-Level-API.xml | 43 +++++++++++++++++++++--------------- 1 file changed, 25 insertions(+), 18 deletions(-) diff --git a/qpid/doc/book/src/High-Level-API.xml b/qpid/doc/book/src/High-Level-API.xml index bf580b2da0..3acaf3fd76 100644 --- a/qpid/doc/book/src/High-Level-API.xml +++ b/qpid/doc/book/src/High-Level-API.xml @@ -73,8 +73,8 @@ A session provides a sequentially ordered context for sending and receiving - messages. A session is created using the - connection.createSession method. + messages. A session is obtained from a + connection. @@ -82,8 +82,7 @@ A sender sends messages to a target using the sender.send method. A sender is - created using the address of the target as a parameter to - the session.createSender method. + obtained from a session for a given target address. @@ -91,9 +90,8 @@ A receiver receives messages from a source using the receiver.fetch method. - A receiver is created using the address of the source as a - parameter to the session.createReceiver - method. + A receiver is obtained from a session for a given source + address. @@ -209,7 +207,7 @@ finally: An address resolves to a node. The - Qpid messaging API has two kinds of nodes, + Qpid messaging API recognises two kinds of nodes, queues and topics. The terms queue and @@ -238,7 +236,16 @@ finally: queues map to AMQP queues, and topics map to AMQP exchanges. - In AMQP 0-10, messages are sent to exchanges, and read from queues. The messaging API also allows a sender to send messages to a queue; internally, Qpid implements this by sending the message to the default exchange, with the name of the queue as the routing key. The messaging API also allows a receiver to receive messages from a topic; internally, Qpid implements this by setting up a private subscription queue for the receiver and binding the subscription queue to the exchange that corresponds to the topic. + In AMQP 0-10, messages are sent to + exchanges, and read from queues. The messaging API also + allows a sender to send messages to a queue; internally, + Qpid implements this by sending the message to the default + exchange, with the name of the queue as the routing key. The + messaging API also allows a receiver to receive messages + from a topic; internally, Qpid implements this by setting up + a private subscription queue for the receiver and binding + the subscription queue to the exchange that corresponds to + the topic. In the rest of this tutorial, we present many examples @@ -349,7 +356,7 @@ Message(properties={spout-id:7da2d27d-93e6-4803-8a61-536d87b8d93f:0}, content='' Address Strings So far, our examples have used address strings that - contain only the address of a node. An address + contain only the name of a node. An address string can also contain a subject and options. @@ -389,13 +396,11 @@ options ::= { : , ... } - At present, subjects are not implemented for AMQP 0-10 - queues in C++ or Python clients. The subject is ignored, and - messages on the queue are received regardless of their - subject. - - In a Java JMS client, the subject is used as a Java JMS - selector when reading from an AMQP 0-10 queue. + At present, receivers will ignore the subject in the the + source address if that address resolves to a queue. Implicit + filtering by subject is only supported for topics and varies + depending on the type of exchange used to represent the + topic. @@ -544,7 +549,9 @@ Message(properties={qpid.subject:usa.faux.news, spout-id:6029430a-cfcb-4700-8e9b Address String Options - Address string options contain policies and extension points such as these: + The options in an address string contain additional + information for the senders or receivers created for it, + including: -- cgit v1.2.1