Tutorial
This tutorial consists of a series of examples using the three most commonly used exchange types - Direct, Fanout and Topic
exchanges. These examples show how to write applications that use the most common messaging paradigms.
- direct
In the direct examples, a message producer writes to the direct exchange, specifying a routing key. A message consumer reads messages from a named queue. This illustrates clean separation of concerns - message producers need to know only the exchange and the routing key, message consumers need to know only which queue to use on the broker.
- fanout
The fanout examples use a fanout exchange and do not use routing keys. Each binding specifies that all messages for a given exchange should be delivered to a given queue.
- pub-sub
In the publish/subscribe examples, a publisher application writes messages to an exchange, specifying a multi-part key. A subscriber application subscribes to messages that match the relevant parts of these keys, using a private queue for each subscription.
- request-response
In the request/response examples, a simple service accepts requests from clients and sends responses back to them. Clients create their own private queues and corresponding routing keys. When a client sends a request to the server, it specifies its own routing key in the reply-to field of the request. The server uses the client's reply-to field as the routing key for the response.
Running the Examples
Before running the examples, you need to unzip the file Qpid.NET-net-2.0-M4.zip, the following tree is created:
| -qpid |
| -lib (contains the required dlls) |
| -examples |
|
|
| |
-example-direct-Listener.exe |
| |
-example-direct-Producer.exe |
|
|
| |
-example-fanout-Listener.exe |
| |
-example-fanout-Producer.exe |
|
|
| |
-example-pub-sub-Listener.exe |
| |
-example-pub-sub-Publisher.exe |
|
|
| -example-request-response-Client.exe |
| -example-request-response-Server.exe |
