Hi Aidan, ----- "Aidan Skinner" <[email protected]> wrote:
> On Fri, Jan 9, 2009 at 2:27 AM, Cliff Jansen (Interop Systems Inc) > <[email protected]> wrote: > >> My impression has been that WCF is purely an RPC abstraction. Does > it > >> offer traditional messaging semantics as well? > > > > Yes. For example, the Microsoft "StockTrader" sample application > uses WCF and MSMQ to provide the same functionality as IBM's "Trade" > sample application using JMS over IBM's Service Integration Bus - i.e. > distributed transactions over durable message queues. > > Interesting. Is it possible to do heterogeneous messaging with this? > Could I have a JMS client on one end and a WCF client on the other > without jumping through a lot of hoops? I it is my understanding that if you have the correct WCF adapters then you can do this. IONA's ART technology was similar to this. the idea is that you can provide a uniform interface to the application programmer in .NET but that various plugins can be configured to provide different protocols or transports for integration with non-.NET platforms. So there could be an IIOP adapter or an FTP adapter or etc. In our case you can have an AMQP adapter. NO the issue with JMS is that JMS doesn't have a standard protocol on the wire and so you would have to have a specific JMS implementation adapter, e.g. an SonicMQ adapter, or a Websphere JMS adapter etc. Of course the great thing about AMQP is that it is an open standard protocol for on the wire. So if JMS vendors start supporting that then the WCF AMQP adapter will work with all of them ;-) Best, William > > - Aidan > -- > Apache Qpid - World Domination through Advanced Message Queueing > http://qpid.apache.org
