On 05/17/2010 04:07 PM, Ted Ross wrote:
The contribution simply allows .NET programs in C#, VB, Powershell,
Excel, etc. to access the Qpid C++ messaging API. It is not in the same
category as the qpid/wcf code which adds substantial value over and
above basic messaging.
The advantage of the thin-binding approach over the existing dotnet
full-client-implementation-in-C# is that it removes the need to support
yet another full-client implementation. The dotnet code is currently
unmaintained, we need a better way to support .NET users.
I agree on both these points[1].
Another aspect of the approach that appeals to me is that it extends the
same concepts that the c++ and python client are built on. This widens
the support base for those questions from .NET users that are not
specific to the .NET interface.
However it also seems sensible to at least consider in this context
whether the WCF functionality could - at some point in the future - be
built on top of this binding[2]. If the WCF stack remains entirely
independent the view that this removes a full-client implementation is
less compelling.
I apologize for committing this patch to trunk without sufficient
debate. I considered this to be more of an added feature to the C++
client and less of a whole-new-direction for .NET.
I understand your point. However, it is another option that we are
potentially offering to .NET users meaning another option we may need to
maintain, document and answer questions for.
Thanks to all those participating in the debate both on this thread and
by Jira; this is exactly what I think we need!
--Gordon
[1] It is probably worth noting though that there are two separate
client implementations in the dotnet directory; one for 0-8 and one for
0-10. The new binding is at present only a valid replacement for the
latter as the c++ client does not support 0-8. Of course now that both
Qpid brokers support 0-10, that is not as big an issue.
[2] That may require some extension of the messaging API of course and
this is being explored on
https://issues.apache.org/jira/browse/QPID-2589 for those interested.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
