qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ken Giusti <kgiu...@redhat.com>
Subject Re: proposed removal of qpid::client API (was Re: QPID code reorg/cleanups - please read.)
Date Fri, 21 Jun 2013 18:02:55 GMT

Good point Bill - I've created a JIRA to cut the console over to the messaging api:

https://issues.apache.org/jira/browse/QPID-4945


Though, technically, I don't think we can easily remove the old client API from the _python_
client.  IIRC, the new messaging api depends on it.



----- Original Message -----
> From: "Bill Freeman" <ke1g.nh@gmail.com>
> To: "users" <users@qpid.apache.org>
> Sent: Friday, June 21, 2013 1:08:29 PM
> Subject: Re: proposed removal of qpid::client API (was Re: QPID code reorg/cleanups -
please read.)
> 
> On Thu, Jun 20, 2013 at 4:46 PM, Andrew Stitcher <astitcher@redhat.com>wrote:
> 
> > I actually thought this was uncontroversial because we've indicated it
> > is a deprecated API for so long. Is there still actually anything that
> > users can't do with the messaging API that can do with the client API?
> >
> > Depending on how you define "users" and "do", yes.  The python QMF
> console.py library uses the old API, and I use the console.py library.  I
> don't actually touch the underlying old API, so a replacement python
> console using the Messaging API that provides the same interface to my code
> would leave me happy.  I don't know whether that can be done with the
> Messaging API or not.  But until there is such a replacement, I'd object to
> removal of the API (as opposed to removal of the documentation, which, from
> my perspective, is already gone).
> 
> Bill
> 

-- 
-K

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message