> -----Original Message----- > From: Gordon Sim [mailto:[email protected]] > > On 05/10/2010 09:33 PM, [email protected] wrote: > > Author: tross > > Date: Mon May 10 20:33:19 2010 > > New Revision: 942892 > > > > URL: http://svn.apache.org/viewvc?rev=942892&view=rev > > Log: > > QPID-2589 - Applied patch from Chuck Rolke. > > This commit adds a new component and yet another approach for .net, > specifically a .net wrapper around the c++ messaging API. > > We also have a wcf client (this also uses some c++ code, but uses the > 0-10 specific API plus some direct use of the internals of > the client), > and two different pure c# clients for 0-8 and 0-10 respectively. > > Four different options each with its own codebase isn't sensible. We > can't maintain them all and it is confusing for users.
Right. This is nuts. > While aspects of this latest approach certainly appeal to me > personally > (the messaging API is better for a number of reasons than the > older API > and wrapping that also keeps the clients more aligned > conceptually), I > think it deserves a bit more debate. Specifically we have to > explicitly > decide as a community whether this new approach is a path we should > pursue. I'm keen to hear the thoughts of Cliff, Aidan and other .net > aficionados. I'm certainly not up to Cliff's level w/ .NET but I agree with Gordon - this new approach is more elegant and probably more maintainable. However, nobody has discussed: - What about the older .NET component(s)? - How might this affect WCF? - Has anyone thought of how to package this? - Does it have any documentation or tests? -Steve --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
