You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Adam Crain <ac...@greenenergycorp.com> on 2010/11/29 16:47:44 UTC
different versions of .NET clients
Hi,
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.
2) The README describes as a native .NET implementation also compatible with
amqp 0.10
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.
thanks!
Adam
RE: different versions of .NET clients
Posted by Steve Huston <sh...@riverace.com>.
Sorry, should have been more specific...
> Thanks for the reply. I just looked at your RC directory and
> downloaded:
>
> http://people.apache.org/~robbie/qpid/0.8/RC3/qpid-dotnet-0-10-0.8.zip
>
> Is the file you intended for me to examine? I only see binary
> artifacts here.
No - that's the same as your original #2.
Unfortunately, you'll need to get the whole big thing:
http://people.apache.org/~robbie/qpid/0.8/RC3/qpid-0.8.tar.gz
The piece you want is in cpp/bindings/qpid/src (I believe).
You'll need to build the regular C++ client first (qpid/cpp/src)
-Steve
> On Mon, Nov 29, 2010 at 12:05 PM, Steve Huston
> <sh...@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-subscribe@qpid.apache.org
> >
> >
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: different versions of .NET clients
Posted by Adam Crain <ac...@greenenergycorp.com>.
Hi Steve,
Thanks for the reply. I just looked at your RC directory and downloaded:
http://people.apache.org/~robbie/qpid/0.8/RC3/qpid-dotnet-0-10-0.8.zip
Is the file you intended for me to examine? I only see binary artifacts
here.
-Adam
On Mon, Nov 29, 2010 at 12:05 PM, Steve Huston <sh...@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-subscribe@qpid.apache.org
>
>
Re: different versions of .NET clients
Posted by Cliff Jansen <cl...@gmail.com>.
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 <sh...@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-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
RE: different versions of .NET clients
Posted by Steve Huston <sh...@riverace.com>.
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-subscribe@qpid.apache.org