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" <[email protected]> > To: "users" <[email protected]> > 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 <[email protected]>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: [email protected] For additional commands, e-mail: [email protected]
