[openamq-dev] OpenAMQ

Martin Sustrik sustrik at imatix.com
Tue Aug 14 14:26:15 CEST 2007


Hi Mousami,

> As per pal.html Queue_bind binds the queue to the exchange. Untill a queue 
> is bound it will not receive any messages. The example amq_client.c is not 
> using this method to bind the queue to exchange. Can you please let me know 
> the reason behind it.

Note that the message is published to "default" exchange (name = ""). 
Default exchange is automatically bound to each newly created queue. It 
is a exchange of "direct" type and the name of the queue is used as the 
routing key for the binding. Refer to AMQP protocol specification for 
details.

> 2)
> Please let me know on which side(sender/receiver application) should the 
> exchange declaration, queue declaration, queue binding, queue consume, these 
> steps take place.

You can you that in any way you like. However, the most common scenario 
is that publisher declares the exchange whereas consumer declares the 
queue, binds it to the exchange and consumers from it.

> 3)
> what should be the value of routing queue, exchange type for a simple sender 
> / receiver application.

Refer to AMQP protocol specification. The exchange/queue model is 
discussed in much detail there. Basically, you choose the exchange type 
and routing keys depending on what kind of message distribution you want 
to achieve.

> 4)
> can we run these applications(sample codes provided in the package) only 
> from visual studio 2003 ?

It should be multiplatform, but as far as I know there are some issues 
with specific versions of MS Visual Studio. Mato, can you elaborate on this?

> 5)
> Can we write the applications using the api you have provided or do we have 
> to depend on pal script to generate the c code.

You can certainly write the code yourself. PAL is just a convenient tool 
that allows us to write test scenarios quickly.

> 6)
> do you provide any pdf other than wireapi.html to give explaination on all 
> the functions that have been declared in the header files.

Once again, have a look at AMQP protocol specification. Most of the 
wireapi functions map directly to AMQP protocol commands.

Find the specification here:

http://www.amqp.org/tikiwiki/tiki-index.php?page=Download

Martin


More information about the openamq-dev mailing list