I'm about to head off for a week, and thought I'd give this topic a bit of a poke with a stick before I did so there's a bit of discussion on the topic before we're deep into M5 territory.
Traditionally, the approach to writing the .Net client has been to transliterate the Java client by hand and slap a random API on top of that. That seems like a bit of a waste of effort to me. I was thinking about using IKVM to load the Java client as a library for the AMQP-level bits and write a native C# implementations of WCF etc. that used that. This has the benefit of using an existing, tested client implementation, reducing the amount of work that needs done and would help us seperate the AMQP specific bits of the Java client out from the JMS specific bits. It also means that the whole client is running in managed code, which is good. What do people think? - Aidan -- Apache Qpid - World Domination through Advanced Message Queueing http://qpid.apache.org --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
