qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jonat...@apache.org
Subject svn commit: r1066676 [5/8] - in /qpid/site/docs/books/trunk: AMQP-Messaging-Broker-CPP-Book/html/ AMQP-Messaging-Broker-CPP-Book/pdf/ AMQP-Messaging-Broker-Java-Book/html/ AMQP-Messaging-Broker-Java-Book/pdf/ Programming-In-Apache-Qpid/html/ Programmin...
Date Wed, 02 Feb 2011 22:58:38 GMT
Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s08.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s08.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s08.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s08.html Wed Feb  2 22:58:35 2011
@@ -1,13 +1,13 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.8. Receiving Messages from Multiple Sources</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch02.html" title="Chapter 2. Using the Qpid Messaging API"><link rel="prev" href="ch02s07.html" title="2.7. Acknowledging Received Messages"><link rel="next" href="ch02s09.html" title="2.9. Transactions"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.8. Receiving Messages from Multiple Sources</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s07.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td width="20%" align="right"> <a accesskey="n" href="ch02s09.html
 ">Next</a></td></tr></table><hr></div><div class="section" title="2.8. Receiving Messages from Multiple Sources"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3039433"></a>2.8. Receiving Messages from Multiple Sources</h2></div></div></div><p>A receiver can only read from one source, but many
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.8. Receiving Messages from Multiple Sources</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch02.html" title="Chapter 2. Using the Qpid Messaging API"><link rel="prev" href="ch02s07.html" title="2.7. Acknowledging Received Messages"><link rel="next" href="ch02s09.html" title="2.9. Transactions"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.8. Receiving Messages from Multiple Sources</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s07.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td width="20%" align="right"> <a accesskey="n" href="ch02s09.html
 ">Next</a></td></tr></table><hr></div><div class="section" title="2.8. Receiving Messages from Multiple Sources"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2619450"></a>2.8. Receiving Messages from Multiple Sources</h2></div></div></div><p>A receiver can only read from one source, but many
       programs need to be able to read messages from many sources. In
       the Qpid Messaging API, a program can ask a session for
       the <span class="quote">&#8220;<span class="quote">next receiver</span>&#8221;</span>; that is, the receiver that is
       responsible for the next available message. The following
-      example shows how this is done in C++, Python, and .NET C#.
+      examples show how this is done in C++, Python, and .NET C#.
       </p><p>Note that to use this pattern you must enable prefetching
       for each receiver of interest so that the broker will send
       messages before a fetch call is made. See
-      <a class="xref" href="ch02s06.html" title="2.6. Receiver Capacity (Prefetch)">Section 2.6, &#8220;Receiver Capacity (Prefetch)&#8221;</a> for more on this.</p><div class="example"><a name="id3039465"></a><p class="title"><b>Example 2.12. Receiving Messages from Multiple Sources</b></p><div class="example-contents"><p>C++:</p><pre class="programlisting">
+      <a class="xref" href="ch02s06.html" title="2.6. Receiver Capacity (Prefetch)">Section 2.6, &#8220;Receiver Capacity (Prefetch)&#8221;</a> for more on this.</p><div class="example"><a name="id2619482"></a><p class="title"><b>Example 2.12. Receiving Messages from Multiple Sources</b></p><div class="example-contents"><p>C++:</p><pre class="programlisting">
 Receiver receiver1 = session.createReceiver(address1);
 receiver1.setCapacity(10);
 Receiver receiver2 = session.createReceiver(address2);

Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s09.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s09.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s09.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s09.html Wed Feb  2 22:58:35 2011
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.9. Transactions</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch02.html" title="Chapter 2. Using the Qpid Messaging API"><link rel="prev" href="ch02s08.html" title="2.8. Receiving Messages from Multiple Sources"><link rel="next" href="ch02s10.html" title="2.10. Connection Options"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.9. Transactions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s08.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td width="20%" align="right"> <a accesskey="n" href="ch02s10.html">Next</a></td></tr></table><hr></div><d
 iv class="section" title="2.9. Transactions"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3039518"></a>2.9. Transactions</h2></div></div></div><p>Sometimes it is useful to be able to group messages
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.9. Transactions</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch02.html" title="Chapter 2. Using the Qpid Messaging API"><link rel="prev" href="ch02s08.html" title="2.8. Receiving Messages from Multiple Sources"><link rel="next" href="ch02s10.html" title="2.10. Connection Options"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.9. Transactions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s08.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td width="20%" align="right"> <a accesskey="n" href="ch02s10.html">Next</a></td></tr></table><hr></div><d
 iv class="section" title="2.9. Transactions"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2619535"></a>2.9. Transactions</h2></div></div></div><p>Sometimes it is useful to be able to group messages
       transfers - sent and/or received - on a session into atomic
       grouping. This can be done be creating the session as
       transactional. On a transactional session sent messages only
@@ -6,17 +6,27 @@
       received and acknowledged messages are only discarded at their
       source on commit
 
-      <sup>[<a name="id3039545" href="#ftn.id3039545" class="footnote">7</a>]</sup>
+      <sup>[<a name="id2619568" href="#ftn.id2619568" class="footnote">8</a>]</sup>
 
-      .</p><div class="example"><a name="id3039555"></a><p class="title"><b>Example 2.13. Transactions</b></p><div class="example-contents"><p>C++:</p><pre class="programlisting">
+      .</p><div class="example"><a name="id2619578"></a><p class="title"><b>Example 2.13. Transactions</b></p><div class="example-contents"><p>C++:</p><pre class="programlisting">
 Connection connection(broker);
 Session session =  connection.createTransactionalSession();
 ...
 if (smellsOk())
    session.commit();
-else 
+else
    session.rollback();
-   </pre></div></div><br class="example-break"><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id3039545" href="#id3039545" class="para">7</a>] </sup>Note that this currently is only true for
+   </pre><p>
+				.NET C#:
+			</p><pre class="programlisting">
+Connection connection = new Connection(broker);
+Session session =  connection.CreateTransactionalSession();
+...
+if (smellsOk())
+   session.Commit();
+else
+   session.Rollback();
+</pre></div></div><br class="example-break"><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2619568" href="#id2619568" class="para">8</a>] </sup>Note that this currently is only true for
       messages received using a reliable mode
       e.g. at-least-once. Messages sent by a broker to a receiver in
       unreliable receiver will be discarded immediately regardless of

Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s10.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s10.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s10.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s10.html Wed Feb  2 22:58:35 2011
@@ -1,9 +1,9 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.10. Connection Options</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch02.html" title="Chapter 2. Using the Qpid Messaging API"><link rel="prev" href="ch02s09.html" title="2.9. Transactions"><link rel="next" href="ch02s11.html" title="2.11. Maps in Message Content"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.10. Connection Options</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s09.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td width="20%" align="right"> <a accesskey="n" href="ch02s11.html">Next</a></td></tr></table><hr></div><div class=
 "section" title="2.10. Connection Options"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="connection-options"></a>2.10. Connection Options</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.10. Connection Options</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch02.html" title="Chapter 2. Using the Qpid Messaging API"><link rel="prev" href="ch02s09.html" title="2.9. Transactions"><link rel="next" href="ch02s11.html" title="2.11. Maps and Lists in Message Content"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.10. Connection Options</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s09.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td width="20%" align="right"> <a accesskey="n" href="ch02s11.html">Next</a></td></tr></table><hr></div><
 div class="section" title="2.10. Connection Options"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="connection-options"></a>2.10. Connection Options</h2></div></div></div><p>
         Aspects of the connections behaviour can be controlled through
         specifying connection options. For example, connections can be
         configured to automatically reconnect if the connection to a
         broker is lost.
-      </p><div class="example"><a name="id3039594"></a><p class="title"><b>Example 2.14. Specifying Connection Options in C++ and Python</b></p><div class="example-contents"><p>In C++, these options can be set using <code class="function">Connection::setOption()</code> or by passing in a set of options to the constructor. The options can be passed in as a map or in string form:</p><pre class="programlisting">
+      </p><div class="example"><a name="id2619630"></a><p class="title"><b>Example 2.14. Specifying Connection Options in C++, Python, and .NET</b></p><div class="example-contents"><p>In C++, these options can be set using <code class="function">Connection::setOption()</code> or by passing in a set of options to the constructor. The options can be passed in as a map or in string form:</p><pre class="programlisting">
 Connection connection("localhost:5672", "{reconnect: true}");
 try {
     connection.open();
@@ -20,17 +20,28 @@ connection = Connection("localhost:5672"
 try:
   connection.open()
   !!! SNIP !!!
-  </pre>
-
-or 
-
-	  <pre class="programlisting">
+  </pre><p>or</p><pre class="programlisting">
 connection = Connection("localhost:5672")
 connection.reconnect = True
 try:
   connection.open()
   !!! SNIP !!!
-  </pre><p>See the reference documentation for details in each language.</p></div></div><br class="example-break"><p>The following table lists the supported connection options.</p><div class="table"><a name="id3039668"></a><p class="title"><b>Table 2.4. Connection Options</b></p><div class="table-contents"><table summary="Connection Options" width="100%" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>option name</th><th>value type</th><th>semantics</th></tr></thead><tbody><tr><td>
+  </pre><p>
+				In .NET, these options can be set using <code class="function">Connection.SetOption()</code> or by passing in a set of options to the constructor. The options can be passed in as a map or in string form:
+			</p><pre class="programlisting">
+Connection connection= new Connection("localhost:5672", "{reconnect: true}");
+try {
+    connection.Open();
+    !!! SNIP !!!
+</pre><p>
+				or
+			</p><pre class="programlisting">
+Connection connection = new Connection("localhost:5672");
+connection.SetOption("reconnect", true);
+try {
+    connection.Open();
+    !!! SNIP !!!
+</pre><p>See the reference documentation for details in each language.</p></div></div><br class="example-break"><p>The following table lists the supported connection options.</p><div class="table"><a name="id2619740"></a><p class="title"><b>Table 2.4. Connection Options</b></p><div class="table-contents"><table summary="Connection Options" width="100%" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>option name</th><th>value type</th><th>semantics</th></tr></thead><tbody><tr><td>
 		  username
 		</td><td>
 		  string
@@ -65,31 +76,31 @@ try:
 		</td><td>
 		  Transparently reconnect if the connection is lost.
 		</td></tr><tr><td>
-		  reconnect_timeout
+		  <code class="literal">reconnect_timeout [Python]</code> <code class="literal">reconnect-timeout [C++]</code>
 		</td><td>
 		  integer
 		</td><td>
 		  Total number of seconds to continue reconnection attempts before giving up and raising an exception.
 		</td></tr><tr><td>
-		  reconnect_limit
+		  <code class="literal">reconnect_limit [Python]</code> <code class="literal">reconnect-limit [C++]</code>
 		</td><td>
 		  integer
 		</td><td>
 		  Maximum number of reconnection attempts before giving up and raising an exception.
 		</td></tr><tr><td>
-		  reconnect_interval_min
+		  <code class="literal">reconnect_interval_min [Python]</code> <code class="literal">reconnect-interval-min [C++]</code>
 		</td><td>
 		  integer representing time in seconds
 		</td><td>
 		  Minimum number of seconds between reconnection attempts. The first reconnection attempt is made immediately; if that fails, the first reconnection delay is set to the value of <code class="literal">reconnect_interval_min</code>; if that attempt fails, the reconnect interval increases exponentially until a reconnection attempt succeeds or <code class="literal">reconnect_interval_max</code> is reached.
 		</td></tr><tr><td>
-		  reconnect_interval_max
+		  <code class="literal">reconnect_interval_max [Python]</code> <code class="literal">reconnect-interval-max [C++]</code>
 		</td><td>
 		  integer representing time in seconds
 		</td><td>
 		  Maximum reconnect interval.
 		</td></tr><tr><td>
-		  reconnect_interval
+		  <code class="literal">reconnect_interval [Python]</code> <code class="literal">reconnect-interval [C++]</code>
 		</td><td>
 		  integer representing time in seconds
 		</td><td>
@@ -114,4 +125,4 @@ try:
 	          boolean
 	        </td><td>
 	          Set tcp no-delay, i.e. disable Nagle algorithm. [C++ only]
-	        </td></tr></tbody></table></div></div><br class="table-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02s09.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch02s11.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.9. Transactions </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.11. Maps in Message Content</td></tr></table></div></body></html>
+	        </td></tr></tbody></table></div></div><br class="table-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02s09.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch02s11.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.9. Transactions </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.11. Maps and Lists in Message Content</td></tr></table></div></body></html>

Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s11.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s11.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s11.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s11.html Wed Feb  2 22:58:35 2011
@@ -1,28 +1,18 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.11. Maps in Message Content</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch02.html" title="Chapter 2. Using the Qpid Messaging API"><link rel="prev" href="ch02s10.html" title="2.10. Connection Options"><link rel="next" href="ch02s12.html" title="2.12. The Request / Response Pattern"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.11. Maps in Message Content</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s10.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td width="20%" align="right"> <a accesskey="n" href="ch02s12.html">Next</a></td></tr></tab
 le><hr></div><div class="section" title="2.11. Maps in Message Content"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="section-Maps"></a>2.11. Maps in Message Content</h2></div></div></div><p>Many messaging applications need to exchange data across
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.11. Maps and Lists in Message Content</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch02.html" title="Chapter 2. Using the Qpid Messaging API"><link rel="prev" href="ch02s10.html" title="2.10. Connection Options"><link rel="next" href="ch02s12.html" title="2.12. The Request / Response Pattern"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.11. Maps and Lists in Message Content</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s10.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td width="20%" align="right"> <a accesskey="n" href="ch02s12.html">Nex
 t</a></td></tr></table><hr></div><div class="section" title="2.11. Maps and Lists in Message Content"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="section-Maps"></a>2.11. Maps and Lists in Message Content</h2></div></div></div><p>Many messaging applications need to exchange data across
       languages and platforms, using the native datatypes of each
-      programming language.</p><p>The Qpid Messaging API supports maps in message
-      content. 
+      programming language.</p><p>The Qpid Messaging API supports <code class="classname">map</code> and <code class="classname">list</code> in message content.
 
-      <sup>[<a name="id3082620" href="#ftn.id3082620" class="footnote">8</a>]</sup>
+      <sup>[<a name="id2662763" href="#ftn.id2662763" class="footnote">9</a>]</sup>
 
-      These maps are supported in each language using
-      the conventions of the language. In Java, we implement the
-      <code class="classname">MapMessage</code> interface
-  
-      <sup>[<a name="id3082631" href="#ftn.id3082631" class="footnote">9</a>]</sup>
-
-      ; in Python, we
-      support <code class="classname">dict</code> and
-      <code class="classname">list</code> in message content; in C++, we
-      provide the <code class="classname">Variant::Map</code> and
-      <code class="classname">Variant::List</code> classes to represent maps
-      and lists. In all languages, messages are encoded using AMQP's
-      portable datatypes.
+			<sup>[<a name="id2662769" href="#ftn.id2662769" class="footnote">10</a>]</sup>
+			Specific language support for <code class="classname">map</code> and <code class="classname">list</code> objects are shown in the following table.
+		 </p><div class="table"><a name="tabl-Programming_in_Apache_Qpid-Qpid_Maps_in_Message_Content"></a><p class="title"><b>Table 2.5. Map and List Representation in Supported Languages</b></p><div class="table-contents"><table summary="Map and List Representation in Supported Languages" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Language</th><th>map</th><th>list</th></tr></thead><tbody><tr><td>Python</td><td><code class="classname">dict</code></td><td><code class="classname">list</code></td></tr><tr><td>C++</td><td><code class="classname">Variant::Map</code></td><td><code class="classname">Variant::List</code></td></tr><tr><td>Java</td><td><code class="classname">MapMessage</code></td><td><code class="classname"> </code></td></tr><tr><td>.NET</td><td><code class="classname">Dictionary&lt;string, object&gt;</code></td><td><code class="classname">Collection&lt;object&gt;</code></td></tr></tbody></table></div></div><br class="table-break"><p>
+			In all languages, messages are encoded using AMQP's portable datatypes.
       </p><div class="tip" title="Tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>Because of the differences in type systems among
       languages, the simplest way to provide portable messages is to
       rely on maps, lists, strings, 64 bit signed integers, and
       doubles for messages that need to be exchanged across languages
-      and platforms.</p></div><div class="section" title="2.11.1. Qpid Maps in Python"><div class="titlepage"><div><div><h3 class="title"><a name="section-Python-Maps"></a>2.11.1. Qpid Maps in Python</h3></div></div></div><p>In Python, Qpid supports the <code class="classname">dict</code> and <code class="classname">list</code> types directly in message content. The following code shows how to send these structures in a message:</p><div class="example"><a name="id3082686"></a><p class="title"><b>Example 2.15. Sending Qpid Maps in Python</b></p><div class="example-contents"><pre class="programlisting">
+      and platforms.</p></div><div class="section" title="2.11.1. Qpid Maps and Lists in Python"><div class="titlepage"><div><div><h3 class="title"><a name="section-Python-Maps"></a>2.11.1. Qpid Maps and Lists in Python</h3></div></div></div><p>In Python, Qpid supports the <code class="classname">dict</code> and <code class="classname">list</code> types directly in message content. The following code shows how to send these structures in a message:</p><div class="example"><a name="id2662920"></a><p class="title"><b>Example 2.15. Sending Qpid Maps and Lists in Python</b></p><div class="example-contents"><pre class="programlisting">
 from qpid.messaging import *
 # !!! SNIP !!!
 
@@ -30,17 +20,17 @@ content = {'Id' : 987654321, 'name' : 'W
 content['colours'] = ['red', 'green', 'white']
 content['dimensions'] = {'length' : 10.2, 'width' : 5.1,'depth' : 2.0};
 content['parts'] = [ [1,2,5], [8,2,5] ]
-content['specs'] = {'colors' : content['colours'], 
-                    'dimensions' : content['dimensions'], 
+content['specs'] = {'colors' : content['colours'],
+                    'dimensions' : content['dimensions'],
                     'parts' : content['parts'] }
 message = Message(content=content)
 sender.send(message)
        </pre></div></div><br class="example-break"><p>The following table shows the datatypes that can be sent in a Python map message,
- and the corresponding datatypes that will be received by clients in Java or C++.</p><div class="table"><a name="table-Python-Maps"></a><p class="title"><b>Table 2.5. Python Datatypes in Maps</b></p><div class="table-contents"><table summary="Python Datatypes in Maps" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Python Datatype</th><th>&#8594; C++</th><th>&#8594; Java</th></tr></thead><tbody><tr><td>bool</td><td>bool</td><td>boolean</td></tr><tr><td>int</td><td>int64</td><td>long</td></tr><tr><td>long</td><td>int64</td><td>long</td></tr><tr><td>float</td><td>double</td><td>double</td></tr><tr><td>unicode</td><td>string</td><td>java.lang.String</td></tr><tr><td>uuid</td><td>qpid::types::Uuid</td><td>java.util.UUID</td></tr><tr><td>dict</td><td>Variant::Map</td><td>java.util.Map</td></tr><tr><td>list</td><td>Variant::List</td><td>java.util.List</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section" title="2.11.2. Qpid Maps i
 n C++"><div class="titlepage"><div><div><h3 class="title"><a name="section-cpp-Maps"></a>2.11.2. Qpid Maps in C++</h3></div></div></div><p>In C++, Qpid defines the the
+ and the corresponding datatypes that will be received by clients in Java or C++.</p><div class="table"><a name="table-Python-Maps"></a><p class="title"><b>Table 2.6. Python Datatypes in Maps</b></p><div class="table-contents"><table summary="Python Datatypes in Maps" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Python Datatype</th><th>&#8594; C++</th><th>&#8594; Java</th></tr></thead><tbody><tr><td>bool</td><td>bool</td><td>boolean</td></tr><tr><td>int</td><td>int64</td><td>long</td></tr><tr><td>long</td><td>int64</td><td>long</td></tr><tr><td>float</td><td>double</td><td>double</td></tr><tr><td>unicode</td><td>string</td><td>java.lang.String</td></tr><tr><td>uuid</td><td>qpid::types::Uuid</td><td>java.util.UUID</td></tr><tr><td>dict</td><td>Variant::Map</td><td>java.util.Map</td></tr><tr><td>list</td><td>Variant::List</td><td>java.util.List</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section" title="2.11.2. Qpid Maps a
 nd Lists in C++"><div class="titlepage"><div><div><h3 class="title"><a name="section-cpp-Maps"></a>2.11.2. Qpid Maps and Lists in C++</h3></div></div></div><p>In C++, Qpid defines the the
 	<code class="classname">Variant::Map</code> and
 	<code class="classname">Variant::List</code> types, which can be
 	encoded into message content. The following code shows how to
-	send these structures in a message:</p><div class="example"><a name="id3082856"></a><p class="title"><b>Example 2.16. Sending Qpid Maps in C++</b></p><div class="example-contents"><pre class="programlisting">
+	send these structures in a message:</p><div class="example"><a name="id2663088"></a><p class="title"><b>Example 2.16. Sending Qpid Maps and Lists in C++</b></p><div class="example-contents"><pre class="programlisting">
 using namespace qpid::types;
 
 // !!! SNIP !!!
@@ -60,38 +50,38 @@ Variant::Map dimensions;
 dimensions["length"] = 10.2;
 dimensions["width"] = 5.1;
 dimensions["depth"] = 2.0;
-content["dimensions"]= dimensions; 
+content["dimensions"]= dimensions;
 
 Variant::List part1;
 part1.push_back(Variant(1));
 part1.push_back(Variant(2));
 part1.push_back(Variant(5));
- 
+
 Variant::List part2;
 part2.push_back(Variant(8));
 part2.push_back(Variant(2));
 part2.push_back(Variant(5));
- 
+
 Variant::List parts;
 parts.push_back(part1);
 parts.push_back(part2);
-content["parts"]= parts; 
+content["parts"]= parts;
 
 Variant::Map specs;
-specs["colours"] = colours; 
-specs["dimensions"] = dimensions; 
-specs["parts"] = parts; 
+specs["colours"] = colours;
+specs["dimensions"] = dimensions;
+specs["parts"] = parts;
 content["specs"] = specs;
 
 encode(content, message);
 sender.send(message, true);
      </pre></div></div><br class="example-break"><p>The following table shows the datatypes that can be sent
 	in a C++ map message, and the corresponding datatypes that
-	will be received by clients in Java and Python.</p><div class="table"><a name="table-cpp-Maps"></a><p class="title"><b>Table 2.6. C++ Datatypes in Maps</b></p><div class="table-contents"><table summary="C++ Datatypes in Maps" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>C++ Datatype</th><th>&#8594; Python</th><th>&#8594; Java</th></tr></thead><tbody><tr><td>bool</td><td>bool</td><td>boolean</td></tr><tr><td>uint16</td><td>int | long</td><td>short</td></tr><tr><td>uint32</td><td>int | long</td><td>int</td></tr><tr><td>uint64</td><td>int | long</td><td>long</td></tr><tr><td>int16</td><td>int | long</td><td>short</td></tr><tr><td>int32</td><td>int | long</td><td>int</td></tr><tr><td>int64</td><td>int | long</td><td>long</td></tr><tr><td>float</td><td>float</td><td>float</td></tr><tr><td>double</td><td>float</td><td>double</td></tr><tr><td>string</td><td>unicode</td><td>java.lang.String</td></tr><tr><td>qpid::types::Uuid</td><td>uuid</td><td>java.util.UUID</t
 d></tr><tr><td>Variant::Map</td><td>dict</td><td>java.util.Map</td></tr><tr><td>Variant::List</td><td>list</td><td>java.util.List</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section" title="2.11.3. Qpid Maps in .NET"><div class="titlepage"><div><div><h3 class="title"><a name="section-dotnet-Maps"></a>2.11.3. Qpid Maps in .NET</h3></div></div></div><p>
+	will be received by clients in Java and Python.</p><div class="table"><a name="table-cpp-Maps"></a><p class="title"><b>Table 2.7. C++ Datatypes in Maps</b></p><div class="table-contents"><table summary="C++ Datatypes in Maps" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>C++ Datatype</th><th>&#8594; Python</th><th>&#8594; Java</th></tr></thead><tbody><tr><td>bool</td><td>bool</td><td>boolean</td></tr><tr><td>uint16</td><td>int | long</td><td>short</td></tr><tr><td>uint32</td><td>int | long</td><td>int</td></tr><tr><td>uint64</td><td>int | long</td><td>long</td></tr><tr><td>int16</td><td>int | long</td><td>short</td></tr><tr><td>int32</td><td>int | long</td><td>int</td></tr><tr><td>int64</td><td>int | long</td><td>long</td></tr><tr><td>float</td><td>float</td><td>float</td></tr><tr><td>double</td><td>float</td><td>double</td></tr><tr><td>string</td><td>unicode</td><td>java.lang.String</td></tr><tr><td>qpid::types::Uuid</td><td>uuid</td><td>java.util.UUID</t
 d></tr><tr><td>Variant::Map</td><td>dict</td><td>java.util.Map</td></tr><tr><td>Variant::List</td><td>list</td><td>java.util.List</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section" title="2.11.3. Qpid Maps and Lists in .NET"><div class="titlepage"><div><div><h3 class="title"><a name="section-dotnet-Maps"></a>2.11.3. Qpid Maps and Lists in .NET</h3></div></div></div><p>
 	  The .NET binding for the Qpid Messaging API binds .NET managed data types
 	  to C++ <code class="classname">Variant</code> data types.  The following code shows how to
 	  send Map and List structures in a message:
-	</p><div class="example"><a name="id3083069"></a><p class="title"><b>Example 2.17. Sending Qpid Maps in .NET C#</b></p><div class="example-contents"><pre class="programlisting">
+	</p><div class="example"><a name="id2663304"></a><p class="title"><b>Example 2.17. Sending Qpid Maps and Lists in .NET C#</b></p><div class="example-contents"><pre class="programlisting">
 using System;
 using Org.Apache.Qpid.Messaging;
 
@@ -158,7 +148,10 @@ Message message = new Message(content);
 Send(message, true);
      </pre></div></div><br class="example-break"><p>
 	  The following table shows the mapping between datatypes in .NET and C++.
-	</p><div class="table"><a name="table-dotnet-Maps"></a><p class="title"><b>Table 2.7. Datatype Mapping between C++ and .NET binding</b></p><div class="table-contents"><table summary="Datatype Mapping between C++ and .NET binding" border="1"><colgroup><col><col></colgroup><thead><tr><th>C++ Datatype</th><th>&#8594; .NET binding</th></tr></thead><tbody><tr><td>void</td><td>nullptr</td></tr><tr><td>bool</td><td>bool</td></tr><tr><td>uint8</td><td>byte</td></tr><tr><td>uint16</td><td>UInt16</td></tr><tr><td>uint32</td><td>UInt32</td></tr><tr><td>uint64</td><td>UInt64</td></tr><tr><td>uint8</td><td>char</td></tr><tr><td>int16</td><td>Int16</td></tr><tr><td>int32</td><td>Int32</td></tr><tr><td>int64</td><td>Int64</td></tr><tr><td>float</td><td>Single</td></tr><tr><td>double</td><td>Double</td></tr><tr><td>string</td><td>string  <a class="co" name="mapping-dotnet-string" href="ch02s11.html#callout-dotnet-string">(1)</a></td></tr><tr><td>qpid::types::Uuid</td><td>Guid</td></tr><t
 r><td>Variant::Map</td><td>Dictionary&lt;string, object&gt;  <a class="co" name="mapping-dotnet-dict-index" href="ch02s11.html#callout-dotnet-string">(2)</a></td></tr><tr><td>Variant::List</td><td>Collection&lt;object&gt;  <a class="co" name="mapping-dotnet-list-value" href="ch02s11.html#callout-dotnet-string">(3)</a></td></tr></tbody></table></div></div><br class="table-break"><div class="calloutlist"><table border="0" summary="Callout list"><tr><td width="5%" valign="top" align="left"><p><a name="callout-dotnet-string"></a><a href="#mapping-dotnet-string">(1)</a> </p></td><td valign="top" align="left"><p>Strings are currently interpreted only with UTF-8 encoding.</p></td></tr></table></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id3082620" href="#id3082620" class="para">8</a>] </sup>Unlike JMS, there is not a specific message type for
-      map messages.</p></div><div class="footnote"><p><sup>[<a name="ftn.id3082631" href="#id3082631" class="para">9</a>] </sup>Note that the Qpid JMS client supports
-      MapMessages whose values can be nested maps or lists. This is
-      not standard JMS behaviour.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02s10.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch02s12.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.10. Connection Options </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.12. The Request / Response Pattern</td></tr></table></div></body></html>
+	</p><div class="table"><a name="table-dotnet-Maps"></a><p class="title"><b>Table 2.8. Datatype Mapping between C++ and .NET binding</b></p><div class="table-contents"><table summary="Datatype Mapping between C++ and .NET binding" border="1"><colgroup><col><col></colgroup><thead><tr><th>C++ Datatype</th><th>&#8594; .NET binding</th></tr></thead><tbody><tr><td>void</td><td>nullptr</td></tr><tr><td>bool</td><td>bool</td></tr><tr><td>uint8</td><td>byte</td></tr><tr><td>uint16</td><td>UInt16</td></tr><tr><td>uint32</td><td>UInt32</td></tr><tr><td>uint64</td><td>UInt64</td></tr><tr><td>uint8</td><td>char</td></tr><tr><td>int16</td><td>Int16</td></tr><tr><td>int32</td><td>Int32</td></tr><tr><td>int64</td><td>Int64</td></tr><tr><td>float</td><td>Single</td></tr><tr><td>double</td><td>Double</td></tr><tr><td>string</td><td>string
+          <sup>[<a name="callout-dotnet-string" href="#ftn.callout-dotnet-string" class="footnote">a</a>]</sup></td></tr><tr><td>qpid::types::Uuid</td><td>Guid</td></tr><tr><td>Variant::Map</td><td>Dictionary&lt;string, object&gt;
+          <sup>[<a href="ch02s11.html#ftn.callout-dotnet-string" class="footnoteref">a</a>]</sup></td></tr><tr><td>Variant::List</td><td>Collection&lt;object&gt;
+          <sup>[<a href="ch02s11.html#ftn.callout-dotnet-string" class="footnoteref">a</a>]</sup></td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div class="footnote"><p><sup>[<a name="ftn.callout-dotnet-string" href="#callout-dotnet-string" class="para">a</a>] </sup>Strings are currently interpreted only with UTF-8 encoding.</p></div></td></tr></tbody></table></div></div><br class="table-break"></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2662763" href="#id2662763" class="para">9</a>] </sup>Unlike JMS, there is not a specific message type for
+      map messages.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2662769" href="#id2662769" class="para">10</a>] </sup>
+				Note that the Qpid JMS client supports MapMessages whose values can be nested maps or lists. This is not standard JMS behaviour.
+			  </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02s10.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch02s12.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.10. Connection Options </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.12. The Request / Response Pattern</td></tr></table></div></body></html>

Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s12.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s12.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s12.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s12.html Wed Feb  2 22:58:35 2011
@@ -1,5 +1,5 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.12. The Request / Response Pattern</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch02.html" title="Chapter 2. Using the Qpid Messaging API"><link rel="prev" href="ch02s11.html" title="2.11. Maps in Message Content"><link rel="next" href="ch02s13.html" title="2.13. Performance Tips"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.12. The Request / Response Pattern</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s11.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td width="20%" align="right"> <a accesskey="n" href="ch02s13.html">Next</a></td></tr>
 </table><hr></div><div class="section" title="2.12. The Request / Response Pattern"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3083302"></a>2.12. The Request / Response Pattern</h2></div></div></div><p>Request / Response applications use the reply-to property,
-      described in <a class="xref" href="ch02s16.html#table-amqp0-10-message-properties" title="Table 2.8. Mapping to AMQP 0-10 Message Properties">Table 2.8, &#8220;Mapping to AMQP 0-10 Message Properties&#8221;</a>, to allow a server
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.12. The Request / Response Pattern</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch02.html" title="Chapter 2. Using the Qpid Messaging API"><link rel="prev" href="ch02s11.html" title="2.11. Maps and Lists in Message Content"><link rel="next" href="ch02s13.html" title="2.13. Performance Tips"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.12. The Request / Response Pattern</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s11.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td width="20%" align="right"> <a accesskey="n" href="ch02s13.html">Next</a>
 </td></tr></table><hr></div><div class="section" title="2.12. The Request / Response Pattern"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2663663"></a>2.12. The Request / Response Pattern</h2></div></div></div><p>Request / Response applications use the reply-to property,
+      described in <a class="xref" href="ch02s16.html#table-amqp0-10-message-properties" title="Table 2.9. Mapping to AMQP 0-10 Message Properties">Table 2.9, &#8220;Mapping to AMQP 0-10 Message Properties&#8221;</a>, to allow a server
       to respond to the client that sent a message. A server sets up a
       service queue, with a name known to clients. A client creates a
       private queue for the server's response, creates a message for a
@@ -7,7 +7,7 @@
       the client's response queue, and sends the request to the
       service queue. The server sends the response to the address
       specified in the request's reply-to property.
-      </p><div class="example"><a name="id3083325"></a><p class="title"><b>Example 2.18. Request / Response Applications in C++</b></p><div class="example-contents"><p>This example shows the C++ code for a client and server
+      </p><div class="example"><a name="id2663686"></a><p class="title"><b>Example 2.18. Request / Response Applications in C++</b></p><div class="example-contents"><p>This example shows the C++ code for a client and server
 	that use the request / response pattern.</p><p>The server creates a service queue and waits for a
 	message to arrive. If it receives a message, it sends a
 	message back to the sender.</p><pre class="programlisting">Receiver receiver = session.createReceiver("service_queue; {create: always}");
@@ -39,4 +39,4 @@ std::cout &lt;&lt; request.getContent() 
 	  </pre><p>The client sends the string <code class="literal">ping</code> to
 	the server. The server sends the response
 	<code class="literal">pong</code> back to the same client, using the
-	<code class="varname">replyTo</code> property.</p></div></div><br class="example-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02s11.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch02s13.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.11. Maps in Message Content </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.13. Performance Tips</td></tr></table></div></body></html>
+	<code class="varname">replyTo</code> property.</p></div></div><br class="example-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02s11.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch02s13.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.11. Maps and Lists in Message Content </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.13. Performance Tips</td></tr></table></div></body></html>

Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s13.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s13.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s13.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s13.html Wed Feb  2 22:58:35 2011
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.13. Performance Tips</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch02.html" title="Chapter 2. Using the Qpid Messaging API"><link rel="prev" href="ch02s12.html" title="2.12. The Request / Response Pattern"><link rel="next" href="ch02s14.html" title="2.14. Cluster Failover"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.13. Performance Tips</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s12.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td width="20%" align="right"> <a accesskey="n" href="ch02s14.html">Next</a></td></tr></table><hr></div><di
 v class="section" title="2.13. Performance Tips"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3083412"></a>2.13. Performance Tips</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Consider prefetching messages for receivers (see
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.13. Performance Tips</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch02.html" title="Chapter 2. Using the Qpid Messaging API"><link rel="prev" href="ch02s12.html" title="2.12. The Request / Response Pattern"><link rel="next" href="ch02s14.html" title="2.14. Cluster Failover"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.13. Performance Tips</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s12.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td width="20%" align="right"> <a accesskey="n" href="ch02s14.html">Next</a></td></tr></table><hr></div><di
 v class="section" title="2.13. Performance Tips"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2663773"></a>2.13. Performance Tips</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Consider prefetching messages for receivers (see
           <a class="xref" href="ch02s06.html" title="2.6. Receiver Capacity (Prefetch)">Section 2.6, &#8220;Receiver Capacity (Prefetch)&#8221;</a>). This helps eliminate roundtrips
           and increases throughput. Prefetch is disabled by default,
           and enabling it is the most effective means of improving

Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s14.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s14.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s14.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s14.html Wed Feb  2 22:58:35 2011
@@ -1,8 +1,8 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.14. Cluster Failover</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch02.html" title="Chapter 2. Using the Qpid Messaging API"><link rel="prev" href="ch02s13.html" title="2.13. Performance Tips"><link rel="next" href="ch02s15.html" title="2.15. Logging"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.14. Cluster Failover</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s13.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td width="20%" align="right"> <a accesskey="n" href="ch02s15.html">Next</a></td></tr></table><hr></div><div class="section" title
 ="2.14. Cluster Failover"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3083498"></a>2.14. Cluster Failover</h2></div></div></div><p>The messaging broker can be run in clustering mode, which provides high reliability through replicating state between brokers in the cluster. If one broker in a cluster fails, clients can choose another broker in the cluster and continue their work. Each broker in the cluster also advertises the addresses of all known brokers
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.14. Cluster Failover</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch02.html" title="Chapter 2. Using the Qpid Messaging API"><link rel="prev" href="ch02s13.html" title="2.13. Performance Tips"><link rel="next" href="ch02s15.html" title="2.15. Logging"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.14. Cluster Failover</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s13.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td width="20%" align="right"> <a accesskey="n" href="ch02s15.html">Next</a></td></tr></table><hr></div><div class="section" title
 ="2.14. Cluster Failover"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2663858"></a>2.14. Cluster Failover</h2></div></div></div><p>The messaging broker can be run in clustering mode, which provides high reliability through replicating state between brokers in the cluster. If one broker in a cluster fails, clients can choose another broker in the cluster and continue their work. Each broker in the cluster also advertises the addresses of all known brokers
 
-<sup>[<a name="id3083511" href="#ftn.id3083511" class="footnote">10</a>]</sup>
+<sup>[<a name="id2663871" href="#ftn.id2663871" class="footnote">11</a>]</sup>
 
-. A client can use this information to dynamically keep the list of reconnection urls up to date.</p><p>In C++, the <code class="classname">FailoverUpdates</code> class provides this functionality:</p><div class="example"><a name="id3083526"></a><p class="title"><b>Example 2.19. Tracking cluster membership</b></p><div class="example-contents"><p>In C++:</p><pre class="programlisting">
+. A client can use this information to dynamically keep the list of reconnection urls up to date.</p><p>In C++, the <code class="classname">FailoverUpdates</code> class provides this functionality:</p><div class="example"><a name="id2663887"></a><p class="title"><b>Example 2.19. Tracking cluster membership</b></p><div class="example-contents"><p>In C++:</p><pre class="programlisting">
 #include &lt;qpid/messaging/FailoverUpdates.h&gt;
 ...
 Connection connection("localhost:5672");
@@ -20,4 +20,15 @@ try:
   connection.open()
   auto_fetch_reconnect_urls(connection)
 
-	</pre></div></div><br class="example-break"><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id3083511" href="#id3083511" class="para">10</a>] </sup>This is done via the amq.failover exchange in AMQP 0-10</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02s13.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch02s15.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.13. Performance Tips </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.15. Logging</td></tr></table></div></body></html>
+	</pre><p>
+				In .NET C#:
+			</p><pre class="programlisting">
+using Org.Apache.Qpid.Messaging;
+...
+connection = new Connection("localhost:5672");
+connection.SetOption("reconnect", true);
+try {
+  connection.Open();
+  FailoverUpdates failover = new FailoverUpdates(connection);
+
+</pre></div></div><br class="example-break"><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2663871" href="#id2663871" class="para">11</a>] </sup>This is done via the amq.failover exchange in AMQP 0-10</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02s13.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch02s15.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.13. Performance Tips </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.15. Logging</td></tr></table></div></body></html>

Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s15.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s15.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s15.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s15.html Wed Feb  2 22:58:35 2011
@@ -1,14 +1,19 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.15. Logging</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch02.html" title="Chapter 2. Using the Qpid Messaging API"><link rel="prev" href="ch02s14.html" title="2.14. Cluster Failover"><link rel="next" href="ch02s16.html" title="2.16. The AMQP 0-10 mapping"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.15. Logging</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s14.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td width="20%" align="right"> <a accesskey="n" href="ch02s16.html">Next</a></td></tr></table><hr></div><div class="section" title="2.
 15. Logging"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3083566"></a>2.15. Logging</h2></div></div></div><p>To simplify debugging, Qpid provides a logging facility
-      that prints out messaging events.</p><div class="section" title="2.15.1. Logging in C++"><div class="titlepage"><div><div><h3 class="title"><a name="id3083576"></a>2.15.1. Logging in C++</h3></div></div></div><p>The Qpidd broker and C++ clients can both use environment
-	variables to enable logging. Use QPID_LOG_ENABLE to set the
-	level of logging you are interested in (trace, debug, info,
-	notice, warning, error, or critical):</p><pre class="screen">
-$ export QPID_LOG_ENABLE="warning+"
-</pre><p>The Qpidd broker and C++ clients use QPID_LOG_OUTPUT to
-      determine where logging output should be sent. This is either a
-      file name or the special values stderr, stdout, or syslog:</p><pre class="screen">
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.15. Logging</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch02.html" title="Chapter 2. Using the Qpid Messaging API"><link rel="prev" href="ch02s14.html" title="2.14. Cluster Failover"><link rel="next" href="ch02s16.html" title="2.16. The AMQP 0-10 mapping"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.15. Logging</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s14.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td width="20%" align="right"> <a accesskey="n" href="ch02s16.html">Next</a></td></tr></table><hr></div><div class="section" title="2.
 15. Logging"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2663943"></a>2.15. Logging</h2></div></div></div><p>To simplify debugging, Qpid provides a logging facility
+      that prints out messaging events.</p><div class="section" title="2.15.1. Logging in C++"><div class="titlepage"><div><div><h3 class="title"><a name="id2663953"></a>2.15.1. Logging in C++</h3></div></div></div><p>
+				The Qpidd broker and C++ clients can both use environment variables to enable logging. Linux and Windows systems use the same named environment variables and values.
+			 </p><p>Use QPID_LOG_ENABLE to set the level of logging you are interested in (trace, debug, info, notice, warning, error, or critical):
+			</p><pre class="screen">
+export QPID_LOG_ENABLE="warning+"
+</pre><p>
+				The Qpidd broker and C++ clients use QPID_LOG_OUTPUT to determine where logging output should be sent. This is either a file name or the special values stderr, stdout, or syslog:
+			</p><pre class="screen">
 export QPID_LOG_TO_FILE="/tmp/myclient.out"
-</pre></div><div class="section" title="2.15.2. Logging in Python"><div class="titlepage"><div><div><h3 class="title"><a name="id3083607"></a>2.15.2. Logging in Python</h3></div></div></div><p>
+</pre><p>
+				From a Windows command prompt, use the following command format to set the environment variables:
+			</p><pre class="screen">
+set QPID_LOG_ENABLE=warning+
+set QPID_LOG_TO_FILE=D:\tmp\myclient.out
+</pre></div><div class="section" title="2.15.2. Logging in Python"><div class="titlepage"><div><div><h3 class="title"><a name="id2664002"></a>2.15.2. Logging in Python</h3></div></div></div><p>
 			The Python client library supports logging using the standard Python logging module. The easiest way to do logging is to use the <span class="command"><strong>basicConfig()</strong></span>, which reports all warnings and errors:
 		</p><pre class="programlisting">from logging import basicConfig
 basicConfig()

Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s16.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s16.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s16.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s16.html Wed Feb  2 22:58:35 2011
@@ -75,7 +75,7 @@
             subject exactly). For more control the x-bindings element
             in the link properties must be used.
           </p></li><li class="listitem"><p>
-            For the XML exchange,<sup>[<a name="id3083805" href="#ftn.id3083805" class="footnote">11</a>]</sup> if a subject is specified it is
+            For the XML exchange,<sup>[<a name="id2664203" href="#ftn.id2664203" class="footnote">12</a>]</sup> if a subject is specified it is
             used as the binding key and an XQuery is defined that
             matches any message with that value for
             qpid.subject. Again this means that only messages whose
@@ -103,7 +103,13 @@
         <code class="varname">mp</code> refers to an AMQP 0-10
         <code class="varname">message-properties</code> struct, and
         <code class="varname">dp</code> refers to an AMQP 0-10
-        <code class="varname">delivery-properties</code> struct.</p><div class="table"><a name="table-amqp0-10-message-properties"></a><p class="title"><b>Table 2.8. Mapping to AMQP 0-10 Message Properties</b></p><div class="table-contents"><table summary="Mapping to AMQP 0-10 Message Properties" width="100%" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Python API</th><th>C++ API</th><th>AMQP 0-10 Property<sup>[<a name="id3083920" href="#ftn.id3083920" class="footnote">a</a>]</sup></th></tr></thead><tbody><tr><td>msg.id</td><td>msg.{get,set}MessageId()</td><td>mp.message_id</td></tr><tr><td>msg.subject</td><td>msg.{get,set}Subject()</td><td>mp.application_headers["qpid.subject"]</td></tr><tr><td>msg.user_id</td><td>msg.{get,set}UserId()</td><td>mp.user_id</td></tr><tr><td>msg.reply_to</td><td>msg.{get,set}ReplyTo()</td><td>mp.reply_to<sup>[<a name="id3083982" href="#ftn.id3083982" class="footnote">b</a>]</sup></td></tr><tr><td>msg.correlation_id</td><td>ms
 g.{get,set}CorrelationId()</td><td>mp.correlation_id</td></tr><tr><td>msg.durable</td><td>msg.{get,set}Durable()</td><td>dp.delivery_mode == delivery_mode.persistent<sup>[<a name="id3084008" href="#ftn.id3084008" class="footnote">c</a>]</sup></td></tr><tr><td>msg.priority</td><td>msg.{get,set}Priority()</td><td>dp.priority</td></tr><tr><td>msg.ttl</td><td>msg.{get,set}Ttl()</td><td>dp.ttl</td></tr><tr><td>msg.redelivered</td><td>msg.{get,set}Redelivered()</td><td>dp.redelivered</td></tr><tr><td>msg.properties</td><td>msg.{get,set}Properties()</td><td>mp.application_headers</td></tr><tr><td>msg.content_type</td><td>msg.{get,set}ContentType()</td><td>mp.content_type</td></tr></tbody><tbody class="footnotes"><tr><td colspan="3"><div class="footnote"><p><sup>[<a name="ftn.id3083920" href="#id3083920" class="para">a</a>] </sup>In these entries, <code class="literal">mp</code> refers to an AMQP message property, and <code class="literal">dp</code> refers to an AMQP delivery proper
 ty.</p></div><div class="footnote"><p><sup>[<a name="ftn.id3083982" href="#id3083982" class="para">b</a>] </sup>The reply_to is converted from the protocol representation into an address.</p></div><div class="footnote"><p><sup>[<a name="ftn.id3084008" href="#id3084008" class="para">c</a>] </sup>Note that msg.durable is a boolean, not an enum.</p></div></td></tr></tbody></table></div></div><br class="table-break"><p>The 0-10 mapping also recognises certain special property
+        <code class="varname">delivery-properties</code> struct.</p><div class="table"><a name="table-amqp0-10-message-properties"></a><p class="title"><b>Table 2.9. Mapping to AMQP 0-10 Message Properties</b></p><div class="table-contents"><table summary="Mapping to AMQP 0-10 Message Properties" width="100%" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Python API</th><th>C++ API
+		<sup>[<a name="id2664314" href="#ftn.id2664314" class="footnote">a</a>]</sup>
+	      </th><th>AMQP 0-10 Property<sup>[<a name="id2664332" href="#ftn.id2664332" class="footnote">b</a>]</sup></th></tr></thead><tbody><tr><td>msg.id</td><td>msg.{get,set}MessageId()</td><td>mp.message_id</td></tr><tr><td>msg.subject</td><td>msg.{get,set}Subject()</td><td>mp.application_headers["qpid.subject"]</td></tr><tr><td>msg.user_id</td><td>msg.{get,set}UserId()</td><td>mp.user_id</td></tr><tr><td>msg.reply_to</td><td>msg.{get,set}ReplyTo()</td><td>mp.reply_to<sup>[<a name="id2664394" href="#ftn.id2664394" class="footnote">c</a>]</sup></td></tr><tr><td>msg.correlation_id</td><td>msg.{get,set}CorrelationId()</td><td>mp.correlation_id</td></tr><tr><td>msg.durable</td><td>msg.{get,set}Durable()</td><td>dp.delivery_mode == delivery_mode.persistent<sup>[<a name="id2664420" href="#ftn.id2664420" class="footnote">d</a>]</sup></td></tr><tr><td>msg.priority</td><td>msg.{get,set}Priority()</td><td>dp.priority</td></tr><tr><td>msg.ttl</td><td>msg.{get,set}Ttl()</td><td>dp.ttl</t
 d></tr><tr><td>msg.redelivered</td><td>msg.{get,set}Redelivered()</td><td>dp.redelivered</td></tr><tr><td>msg.properties</td><td>msg.{get,set}Properties()</td><td>mp.application_headers</td></tr><tr><td>msg.content_type</td><td>msg.{get,set}ContentType()</td><td>mp.content_type</td></tr></tbody><tbody class="footnotes"><tr><td colspan="3"><div class="footnote"><p><sup>[<a name="ftn.id2664314" href="#id2664314" class="para">a</a>] </sup>
+		    The .NET Binding for C++ Messaging provides all the
+		    message and delivery properties described in the C++ API.
+		    See  <a class="xref" href="ch05s03.html#table-Dotnet-Binding-Message" title="Table 5.13. .NET Binding for the C++ Messaging API Class: Message">Table 5.13, &#8220;.NET Binding for the C++ Messaging API Class: Message&#8221;</a> .
+	          </p></div><div class="footnote"><p><sup>[<a name="ftn.id2664332" href="#id2664332" class="para">b</a>] </sup>In these entries, <code class="literal">mp</code> refers to an AMQP message property, and <code class="literal">dp</code> refers to an AMQP delivery property.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2664394" href="#id2664394" class="para">c</a>] </sup>The reply_to is converted from the protocol representation into an address.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2664420" href="#id2664420" class="para">d</a>] </sup>Note that msg.durable is a boolean, not an enum.</p></div></td></tr></tbody></table></div></div><br class="table-break"><p>The 0-10 mapping also recognises certain special property
       keys. If the properties contain entries for <code class="literal">x-amqp-0-10.app-id</code>
       or <code class="literal">x-amqp-0-10.content-encoding</code>, the values will be used to
       set <code class="literal">message-properties.app-id</code> and
@@ -112,7 +118,7 @@
       transfer has those properties set, they will be exposed in the
       same manner. In addition the routing key on incoming transfers
       will be exposed directly via the custom property with key
-      <code class="literal">x-amqp-0-10.routing-key</code>.</p><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id3083805" href="#id3083805" class="para">11</a>] </sup>Note that the XML
+      <code class="literal">x-amqp-0-10.routing-key</code>.</p><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2664203" href="#id2664203" class="para">12</a>] </sup>Note that the XML
             exchange is not a standard AMQP exchange type. It is a
             Qpid extension and is currently only supported by the C++
             broker.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02s15.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.15. Logging </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 3. Using the Qpid JMS client</td></tr></table></div></body></html>

Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03.html Wed Feb  2 22:58:35 2011
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 3. Using the Qpid JMS client</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="index.html" title="Programming in Apache Qpid"><link rel="prev" href="ch02s16.html" title="2.16. The AMQP 0-10 mapping"><link rel="next" href="ch03s02.html" title="3.2. Apache Qpid JNDI Properties for AMQP Messaging"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 3. Using the Qpid JMS client</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s16.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch03s02.html">Next</a></td></tr></table><hr></div><div c
 lass="chapter" title="Chapter 3. Using the Qpid JMS client"><div class="titlepage"><div><div><h2 class="title"><a name="QpidJMS"></a>Chapter 3. Using the Qpid JMS client</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch03.html#id3084118">3.1. A Simple Messaging Program in Java JMS</a></span></dt><dt><span class="section"><a href="ch03s02.html">3.2. Apache Qpid JNDI Properties for AMQP Messaging</a></span></dt><dd><dl><dt><span class="section"><a href="ch03s02.html#id3084697">3.2.1. JNDI Properties for Apache Qpid</a></span></dt><dt><span class="section"><a href="ch03s02.html#id3084806">3.2.2. Connection URLs</a></span></dt></dl></dd><dt><span class="section"><a href="ch03s03.html">3.3. Java JMS Message Properties</a></span></dt><dt><span class="section"><a href="ch03s04.html">3.4. JMS MapMessage Types</a></span></dt><dt><span class="section"><a href="ch03s05.html">3.5. JMS Client Logging</a></span></dt></dl></
 div><div class="section" title="3.1. A Simple Messaging Program in Java JMS"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3084118"></a>3.1. A Simple Messaging Program in Java JMS</h2></div></div></div><p>The following program shows how to send and receive a
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 3. Using the Qpid JMS client</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="index.html" title="Programming in Apache Qpid"><link rel="prev" href="ch02s16.html" title="2.16. The AMQP 0-10 mapping"><link rel="next" href="ch03s02.html" title="3.2. Apache Qpid JNDI Properties for AMQP Messaging"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 3. Using the Qpid JMS client</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s16.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch03s02.html">Next</a></td></tr></table><hr></div><div c
 lass="chapter" title="Chapter 3. Using the Qpid JMS client"><div class="titlepage"><div><div><h2 class="title"><a name="QpidJMS"></a>Chapter 3. Using the Qpid JMS client</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch03.html#id2664530">3.1. A Simple Messaging Program in Java JMS</a></span></dt><dt><span class="section"><a href="ch03s02.html">3.2. Apache Qpid JNDI Properties for AMQP Messaging</a></span></dt><dd><dl><dt><span class="section"><a href="ch03s02.html#id2664943">3.2.1. JNDI Properties for Apache Qpid</a></span></dt><dt><span class="section"><a href="ch03s02.html#section-jms-connection-url">3.2.2. Connection URLs</a></span></dt></dl></dd><dt><span class="section"><a href="ch03s03.html">3.3. Java JMS Message Properties</a></span></dt><dt><span class="section"><a href="ch03s04.html">3.4. JMS MapMessage Types</a></span></dt><dt><span class="section"><a href="ch03s05.html">3.5. JMS Client Logging</a></
 span></dt><dt><span class="section"><a href="ch03s06.html">3.6. Configuring the JMS Client</a></span></dt><dd><dl><dt><span class="section"><a href="ch03s06.html#id2666102">3.6.1. Qpid JVM Arguments</a></span></dt></dl></dd></dl></div><div class="section" title="3.1. A Simple Messaging Program in Java JMS"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2664530"></a>3.1. A Simple Messaging Program in Java JMS</h2></div></div></div><p>The following program shows how to send and receive a
       message using the Qpid JMS client. JMS programs typically use
       JNDI to obtain connection factory and destination objects which
       the application needs. In this way the configuration is kept
@@ -8,7 +8,7 @@
       destination from the JNDI context. Then we create a producer and
       a consumer, send a message with the producer and receive it with
       the consumer. This code should be straightforward for anyone
-      familiar with Java JMS.</p><div class="example"><a name="id3084143"></a><p class="title"><b>Example 3.1. "Hello world!" in Java</b></p><div class="example-contents"><pre lang="java" class="programlisting">
+      familiar with Java JMS.</p><div class="example"><a name="id2664555"></a><p class="title"><b>Example 3.1. "Hello world!" in Java</b></p><div class="example-contents"><pre lang="java" class="programlisting">
 package org.apache.qpid.example.jmsexample.hello;
 
 import javax.jms.*;
@@ -32,7 +32,7 @@ public class Hello {
       properties.load(this.getClass().getResourceAsStream("hello.properties"));  <a class="co" name="hello-java-properties" href="ch03.html#callout-java-properties">(1)</a>
       Context context = new InitialContext(properties);   <a class="co" name="hello-java-context" href="ch03.html#callout-java-context">(2)</a>
 
-      ConnectionFactory connectionFactory 
+      ConnectionFactory connectionFactory
           = (ConnectionFactory) context.lookup("qpidConnectionfactory"); <a class="co" name="hello-java-connection-factory" href="ch03.html#callout-java-connection-factory">(3)</a>
       Connection connection = connectionFactory.createConnection();  <a class="co" name="hello-java-connection" href="ch03.html#callout-java-connection">(4)</a>
       connection.start();  <a class="co" name="hello-java-start" href="ch03.html#callout-java-start">(5)</a>
@@ -57,12 +57,12 @@ public class Hello {
     }
   }
 }
-	</pre></div></div><br class="example-break"><div class="calloutlist"><table border="0" summary="Callout list"><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-properties"></a><a href="#hello-java-properties">(1)</a> </p></td><td valign="top" align="left"><p>Loads the JNDI properties file, which specifies connection properties, queues, topics, and addressing options. See <a class="xref" href="ch03s02.html" title="3.2. Apache Qpid JNDI Properties for AMQP Messaging">Section 3.2, &#8220;Apache Qpid JNDI Properties for AMQP Messaging&#8221;</a> for details.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-context"></a><a href="#hello-java-context">(2)</a> </p></td><td valign="top" align="left"><p>Creates the JNDI initial context.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-connection-factory"></a><a href="#hello-java-connection-factory">(3)</a> </p></td><td valign="top" align="left">
 <p>Creates a JMS connection factory for Qpid.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-connection"></a><a href="#hello-java-connection">(4)</a> </p></td><td valign="top" align="left"><p>Creates a JMS connection.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-start"></a><a href="#hello-java-start">(5)</a> </p></td><td valign="top" align="left"><p>Activates the connection.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-session"></a><a href="#hello-java-session">(6)</a> </p></td><td valign="top" align="left"><p>Creates a session. This session is not transactional (transactions='false'), and messages are automatically acknowledged.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-destination"></a><a href="#hello-java-destination">(7)</a> </p></td><td valign="top" align="left"><p>Creates a destination for the topic exchange, so sender
 s and receivers can use it.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-producer"></a><a href="#hello-java-producer">(8)</a> </p></td><td valign="top" align="left"><p>Creates a producer that sends messages to the topic exchange.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-consumer"></a><a href="#hello-java-consumer">(9)</a> </p></td><td valign="top" align="left"><p>Creates a consumer that reads messages from the topic exchange.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-receive"></a><a href="#hello-java-receive">(10)</a> </p></td><td valign="top" align="left"><p>Reads the next available message.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-close"></a><a href="#hello-java-close">(11)</a> </p></td><td valign="top" align="left"><p>Closes the connection, all sessions managed by the connection, and all senders and receivers ma
 naged by each session.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-jndi-close"></a><a href="#hello-java-jndi-close">(12)</a> </p></td><td valign="top" align="left"><p>Closes the JNDI context.</p></td></tr></table></div><p>The contents of the hello.properties file are shown below.</p><div class="example"><a name="id3084575"></a><p class="title"><b>Example 3.2. JNDI Properties File for "Hello world!" example</b></p><div class="example-contents"><pre class="programlisting">
-java.naming.factory.initial 
+	</pre></div></div><br class="example-break"><div class="calloutlist"><table border="0" summary="Callout list"><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-properties"></a><a href="#hello-java-properties">(1)</a> </p></td><td valign="top" align="left"><p>Loads the JNDI properties file, which specifies connection properties, queues, topics, and addressing options. See <a class="xref" href="ch03s02.html" title="3.2. Apache Qpid JNDI Properties for AMQP Messaging">Section 3.2, &#8220;Apache Qpid JNDI Properties for AMQP Messaging&#8221;</a> for details.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-context"></a><a href="#hello-java-context">(2)</a> </p></td><td valign="top" align="left"><p>Creates the JNDI initial context.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-connection-factory"></a><a href="#hello-java-connection-factory">(3)</a> </p></td><td valign="top" align="left">
 <p>Creates a JMS connection factory for Qpid.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-connection"></a><a href="#hello-java-connection">(4)</a> </p></td><td valign="top" align="left"><p>Creates a JMS connection.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-start"></a><a href="#hello-java-start">(5)</a> </p></td><td valign="top" align="left"><p>Activates the connection.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-session"></a><a href="#hello-java-session">(6)</a> </p></td><td valign="top" align="left"><p>Creates a session. This session is not transactional (transactions='false'), and messages are automatically acknowledged.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-destination"></a><a href="#hello-java-destination">(7)</a> </p></td><td valign="top" align="left"><p>Creates a destination for the topic exchange, so sender
 s and receivers can use it.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-producer"></a><a href="#hello-java-producer">(8)</a> </p></td><td valign="top" align="left"><p>Creates a producer that sends messages to the topic exchange.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-consumer"></a><a href="#hello-java-consumer">(9)</a> </p></td><td valign="top" align="left"><p>Creates a consumer that reads messages from the topic exchange.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-receive"></a><a href="#hello-java-receive">(10)</a> </p></td><td valign="top" align="left"><p>Reads the next available message.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-close"></a><a href="#hello-java-close">(11)</a> </p></td><td valign="top" align="left"><p>Closes the connection, all sessions managed by the connection, and all senders and receivers ma
 naged by each session.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-jndi-close"></a><a href="#hello-java-jndi-close">(12)</a> </p></td><td valign="top" align="left"><p>Closes the JNDI context.</p></td></tr></table></div><p>The contents of the hello.properties file are shown below.</p><div class="example"><a name="id2664821"></a><p class="title"><b>Example 3.2. JNDI Properties File for "Hello world!" example</b></p><div class="example-contents"><pre class="programlisting">
+java.naming.factory.initial
   = org.apache.qpid.jndi.PropertiesFileInitialContextFactory
 
 # connectionfactory.[jndiname] = [ConnectionURL]
-connectionfactory.qpidConnectionfactory 
+connectionfactory.qpidConnectionfactory
   = amqp://guest:guest@clientid/test?brokerlist='tcp://localhost:5672' <a class="co" name="hello-properties-connectionfactory" href="ch03.html#callout-hello-properties-connectionfactory">(1)</a>
 # destination.[jndiname] = [address_string]
 destination.topicExchange = amq.topic <a class="co" name="hello-properties-destination" href="ch03.html#callout-hello-properties-destination">(2)</a>



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:commits-subscribe@qpid.apache.org


Mime
View raw message