There are a host of inflight JIRAs for the Broker 0-10 work - but its not a short list. Its top priority for me.
Marnie On Tue, May 18, 2010 at 3:46 PM, Carl Trieloff <[email protected]>wrote: > On 05/18/2010 10:37 AM, Marnie McCormack wrote: > >> I'll confess that I'm fairly uncomfortable with any other new .Net API, >> especially since the current situation is that we have no client which can >> interop across both brokers with all the other clients successfully (with >> the Java Broker 0-10 code not yet complete/prod ready). I'd rather been >> hoping we could get behind the new WCF client and build that out as the >> replacement for the existing .Net components. >> >> > > > I think the new WCF client is the direction. however it is bound directly > to the old C++ 0-10 AMQP, and should at some point to updated to > use the version independent API on the C++ side. > > My view is that it mainly about follow-through, and am glad to see Gordon > and Cliff discussing the issues that need to be addressed to do that. > > The way to get the Java broker to talk WCF, without client proliferation > should > be to complete the 0-10 work on the Java broker. > > Carl. > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > >
