On 02/24/2010 09:00 AM, Cliff Jansen (Interop Systems Inc) wrote:
The easiest way to think of it is that there are two programming
models. The "channel model" is at the lower level and has variations
of send and receive that are analogous to session.messageTransfer()
and localQueue.get(). WcfPerftest.cs is an example and it should be
very easy to follow if you are at all familiar with the C++
perftest.cpp program.
The second programming model, the "service model", is built on top of
that and has fancy features for handling incoming messages and
imposing structure on message content to allow contracts between
clients and servers and discovery of available services.
Ok, that is very helpful already.
[snip]
The samples both use "amqp:<exchange_name>?routingkey=<routing_key>"
when sending and "amqp:<queue_name>" when receiving messages. How does
the binding (in the AMQP sense) happen?
At the moment this has to be done outside WCF using external tools
like the python qpid-config command or a custom C++ program. Near
term feature work will allow creating temporary queues on the fly for
subscribers to topic exchanges or associating a temporary response
queue with a WCF channel. Further out, the plan is to supply
PowerShell commands to do more sophisticated management, which can in
turn be called from GUI management consoles or invoked from within
applications.
It would be good to see if we could use the address syntax the c++ and
python clients now use (indeed I believe the JMS client can be
configured with the same syntax also now).
[snip]
I hope this helps.
It certainly does, thank you very much Cliff!
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
