Perhaps it would be useful for somebody to assist this debate by introducing the messaging API in the .NET context and addressing why, for example, .NET programmers need this API, but Java programmers don't. Or why a developer who might be inclined to use WCF should use this messaging API instead.
Looking at the initial code drop, I have a very hard time imagining a .NET programmer who might feel remotely comfortable using it. This is not a comment on the quality or functionality of the module, just on the utter disregard for basic .NET conventions of the C++ API as transposed to .NET, i.e. the surface area of the library. I don't think it would take a lot of work to address this. The question remains whether this new client intends to ignore distributed transactions, including the new promotable transactions in AMQP 1.0. But compared to the existing dotnet client, from a practical point of view, a module whose heavy lifting is largely done in the C++ space will automatically benefit from bug fixes to that code base. This beats the current dotnet mechanism of running a code translator against a Java snapshot every other year. Carl Trieloff wrote: > The current WCF uses the 0-10 API, I would suggest moving the WCF client > to the updated C++ API. I believe this has been agreed to be done at some > point before on the list which would then be consistent with this work Actually the current WCF implementation uses the 0-10 C++ API where convenient and bypasses it when necessary. The complete lack of distributed transaction support in the updated C++ API means that even more "behind the scenes" work will be required. But wherever possible, the new messaging API would be used. Regardless of recent events, the "Interop" layer of the WCF channel was known to need rewriting for AMQP 1.0. I had hoped that the rewrite would lead to a 0-10 and 1.0 friendly library which, surprise, looks much like this messaging API plus qpid-config. But, realistically, that would happen after many of the other TODO items in the WCF Reame file were done. Cliff --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
