Hi Adam, Adding to Steve's comments, the WCF implementation in qpid/0.6/qpid-dotnet-0-10-0.6.zip is a simple wrapper suitable for Windows to Windows client use only and lacks the underpinning architecture to do distraibuted transactions at all or local trasactions outside the channel model programming style.
The C++ based WCF channel was designed for interoperability, performance and distributed transactions capability. However, since the transaction model is radically different in AMQP 1.0 compared to 0-10, the work to port this forward to AMQP 1.0 is considerable and currently unfunded. This client is your best choice if you prefer to use WCF, and your only choice if you need System.Transactions support. Your most future-proof course of action is to use http://qpid.apache.org/books/0.7/Programming-In-Apache-Qpid/html/ch05.html. The ".NET Binding for the C++ Messaging Client" provides the Qpid messaging api in .NET form. Cliff On Mon, Nov 29, 2010 at 9:05 AM, Steve Huston <shus...@riverace.com> wrote: > Hi Adam, > >> There appear to be two different .NET clients available: >> >> 1) http://apache.cyberuse.com//qpid/0.6/qpid-wcf-0.6.zip >> >> 2) http://apache.cyberuse.com//qpid/0.6/qpid-dotnet-0-10-0.6.zip >> >> 1) appears to be a .NET/WCF wrapper around the C++ client (is >> this correct?). I have gotten this to compile and run. > > Correct. > >> 2) The README describes as a native .NET implementation also >> compatible with amqp 0.10 > > Also correct. Though #2 does not get much attention or maintenance. My > history is sketchy on this, but my undestanding is #2 started as a > translation of the Java client; again, I believe it doesn't get much > attention. > >> Downloading 2), there appears to be no source in the >> distribution, although the README claims that the following >> folder should exist after unpacking: >> >> ******* >> Generate code from <project home>/dotnet/client-010/gentool: >> >> $ cd <project home>/dotnet/client-010/gentool >> $ ant >> ******* >> >> In the distro there are two folders, examples and lib, that >> only contain binary artifacts. >> >> What are the major differences between these two >> implementations from an API perspective? I've been using the >> java client extensively and now want to provide .NET support. > > If I were you and wanted to program to a .NET model instead of WCF > model, I'd look more at the .NET binding in the forthcoming 0.8. You can > grab a release candidate from > http://people.apache.org/~robbie/qpid/0.8/RC3/. It's not a nice Windows > installer yet so you'll need to build it from source, but I think you'll > find it a closer model to what you want. > > If you want to be a guinea pig for an installer for this, let me know. > > -Steve > > -- > Steve Huston, Riverace Corporation > Total Lifecycle Support for Your Networked Applications > http://www.riverace.com > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:users-subscr...@qpid.apache.org > > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@qpid.apache.org
