Ted Ross wrote: > Regarding the .Net client in general... It's my understanding that > there are some contributors at Microsoft that are working on this part > of the code but I don't know what the status of that work is. Maybe > somebody who knows will chime in.
Since David Ingham has just become a proud father and is spending time with family, I will do the chiming. Microsoft's efforts are actually focused towards the qpid/cpp branch of the source code. In addition to the cmake and installation work that Steve Huston has recently done, there is ongoing work to provide a persistence layer for the C++ broker on Windows. Microsoft is also using the Qpid C++ code as a base for client support on Windows. There is work in progress to provide a .NET WCF Channel that is layered on top of the qpidclient.dll and qpidcommon.dll libraries, with support for both XML Infoset and binary encoded message formats and providing an associated resource manager for single and multi-phase transaction support. We are hopeful that this WCF Channel design will gel sufficiently in the very near future (a few weeks?) to be able to provide a detailed outline and fledgling code for review and comment by the Qpid community. Cliff -----Original Message----- From: Ted Ross [mailto:[email protected]] Sent: Friday, June 26, 2009 11:48 AM To: [email protected] Subject: Re: .Net client lib status Julien, Thanks for sending a reminder about your Jira/patch. You are using the right process, we were just a bit slow on the uptake. I'll take a look at that issue. Regarding the .Net client in general... It's my understanding that there are some contributors at Microsoft that are working on this part of the code but I don't know what the status of that work is. Maybe somebody who knows will chime in. Regards, -Ted Julien Lavigne du Cadet wrote: > Dear Commiters, > > I wonder what the status of the .Net client lib is as I’m starting to make > extensive use of it for several in-house applications. > As far as I can tell, there have been minimal updates since December, except > for the QMF patch. Is someone maintaining it? > > I discovered several potential problems in the current implementation for > which I’d like to submit patches : > - Fixes in the UUID class (which has very strong problems IMHO) > - Adding interfaces to simplify testing > - Renaming to follow the .Net convention (if that is acceptable of course) > - And potentially more (for instance, I have my own partial implementation of > QMF which is a lot more “.Net” oriented than the one submitted) > > However, I submitted a first patch to see if it would be integrated before > sending more but the issue is still unresolved > http://issues.apache.org/jira/browse/QPID-1897 2 weeks after. (Of course I’m > perfectly happy if there’s good reason not to integrate it J) > > Is there a specific process I should follow to submit patches? > > Best regards, > > Julien Lavigne du Cadet > ______________________________________ > Sent from my www.pageflakes.com startpage > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
