Sure, we currently have two clients for .NET in Qpid - one for 0-8 and one for 0-10. I know of several users of the 0-8 client, some of whom are discussing their requirements for this year. I hope what follows is a reasonably accurate picture of where we are now.
I think I'm on safe ground stating that the 0-8 client is getting pretty rusty - it was essentially a port of the Java client at the time and has not kept pace. It more or less does what it needs to for the existing users, but it needs some significant attention to bring it up to speed. It also lacks sufficient test cases/docs/etc. The 0-10 client (afaik) is completely separate codebase and has recently had a few teething issues. I know there were some discussions about the need for test cases/docs/interop test integration etc. I'm not sure what the outcome of these threads were, though I see there are some docs and info on running tests on the wiki. We have (to the best of my knowledge) no requriements spec for either implementation, functional or non-functional. So, I think we need to discuss how we're taking the .NET client forward including: - identify what the key differences between the client implementations are (beyond protocol versions etc) - discuss migration paths for existing users - version negotiation/future proofing ? - testing, including the interop test runner integration - active commiters/contributers for the .NET - known use cases we should address At the end, I'd like us to have a strategy we are all happy with and a clear development roadmap for .NET users. Ideally this session would also allow some of our new windows developers to get involved and to influence what we're doing with the client. Hope this sheds some light, Marnie On Thu, Jan 8, 2009 at 10:08 AM, Gordon Sim <[email protected]> wrote: > Marnie McCormack wrote: > >> We are currently in a somewhat interesting situation wrt to .NET clients >> in >> Qpid. >> > > Could you elaborate on the issues? >
