Anyone want to volunteer to take on the Python or Ruby?

-- Rob

On 24/05/07, Rupert Smith <[EMAIL PROTECTED]> wrote:
Interop tests available on Java and C++, a .Net port is in the pipeline but
not started yet.

On 24/05/07, Marnie McCormack <[EMAIL PROTECTED]> wrote:
>
> I guess the more 'how long is a piece of string' like question is around
> interop ? (Sorry) I'm a bit detached from progress that Rupert's been
> making
> on that front ?
>
> Also, there's the python and ruby clients. On account of the votes (and my
> ignorance of the binding process with components in votes for releases) we
> are currently compelled to include them. I guess that means they need to
> work well with both brokers, or we vote to reduce the scope of the
> release,
> as well as be doc'd enough for users ?
>
> Bfn,
> Regards,
> Marnie
>
>
> On 5/24/07, Martin Ritchie <[EMAIL PROTECTED]> wrote:
> >
> > I've been trying to tidy up the Java side also. With some recent
> > functional additions but mainly it has been fixing the odd bug. There
> > are a couple of additions that should be JIRAed that would be good to
> > go in with M2 such as the Mina upgrade(QPID-92) along with limiting
> > the size of our send/receive buffers so we reduce the OOM issues with
> > mina, and QPID-465 for JMS compliance.
> >
> > We also have a bug in the client where FailoverExceptions can 'escape'
> > as not all client api calls correctly handle failover,QPID-402.
> >
> > The other serious issue is an un-JIRAed item about our implementation
> > of AMQMessage on the server side. When used in Pub Sub or delivered to
> > multiple queues then looks like we have a problem.
> >
> > Fixing those along with my current work load will probably take us to
> mid
> > June.
> >
> > On 23/05/07, Gordon Sim <[EMAIL PROTECTED]> wrote:
> > > Rajith Attapattu wrote:
> > > > Alan can u comment on the c++ side. If  I am not mistaken Alan havwe
> > > > already
> > > > identified JIRA's for M2 and is in the process of fixing them.
> > >
> > > Alan is on holiday this week. However we have a fix to the apr_pool
> > > related concurrency issue, channel.flow is implemented and the interop
> > > tests are written. That more or less covers the open JIRAs I think...
> a
> > > couple of them are still marked open as I haven't merged back to trunk
> > > yet (due to other stuff I've got on the go on trunk!).
> > >
> >
> >
> > --
> > Martin Ritchie
> >
>

Reply via email to