You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Ken Giusti <kg...@redhat.com> on 2013/06/21 20:02:55 UTC
Re: proposed removal of qpid::client API (was Re: QPID code
reorg/cleanups - please read.)
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" <ke...@gmail.com>
> To: "users" <us...@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 <as...@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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: proposed removal of qpid::client API (was Re: QPID code
reorg/cleanups - please read.)
Posted by Andrew Stitcher <as...@redhat.com>.
On Fri, 2013-06-21 at 14:27 -0400, Chuck Rolke wrote:
> Not to forget that the WCF project also links to qpidclient. Would the proposed changes retire WCF as well?
I don't think so - the WCF build is entirely internal to qpid and the
header files are still present internally (after all the messaging API
itself depends on the client API internally).
So since WCF isn't dependent on the exported header files I think it'd
still be ok.
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: proposed removal of qpid::client API (was Re: QPID code
reorg/cleanups - please read.)
Posted by Andrew Stitcher <as...@redhat.com>.
On Fri, 2013-06-21 at 14:27 -0400, Chuck Rolke wrote:
> Not to forget that the WCF project also links to qpidclient. Would the proposed changes retire WCF as well?
I don't think so - the WCF build is entirely internal to qpid and the
header files are still present internally (after all the messaging API
itself depends on the client API internally).
So since WCF isn't dependent on the exported header files I think it'd
still be ok.
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: proposed removal of qpid::client API (was Re: QPID code
reorg/cleanups - please read.)
Posted by Chuck Rolke <cr...@redhat.com>.
Not to forget that the WCF project also links to qpidclient. Would the proposed changes retire WCF as well?
-Chuck
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: proposed removal of qpid::client API (was Re: QPID code
reorg/cleanups - please read.)
Posted by Andrew Stitcher <as...@redhat.com>.
On Fri, 2013-06-21 at 14:02 -0400, Ken Giusti wrote:
> 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.
Can we be really careful about our use of words here.
We can't remove the *library* dependency here (and there is no current
proposal to do this) but the python client has no API dependency on the
old client API.
In other words: The swigged libraries do not need us to ship any C++
header files let alone the obsolete client headers files.
*There is no proposal to stop "shipping" the qpid client library
functionality where it is internally used by other libraries with
supported APIs.*
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: proposed removal of qpid::client API (was Re: QPID code
reorg/cleanups - please read.)
Posted by Andrew Stitcher <as...@redhat.com>.
On Fri, 2013-06-21 at 14:02 -0400, Ken Giusti wrote:
> 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.
Can we be really careful about our use of words here.
We can't remove the *library* dependency here (and there is no current
proposal to do this) but the python client has no API dependency on the
old client API.
In other words: The swigged libraries do not need us to ship any C++
header files let alone the obsolete client headers files.
*There is no proposal to stop "shipping" the qpid client library
functionality where it is internally used by other libraries with
supported APIs.*
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: proposed removal of qpid::client API (was Re: QPID code
reorg/cleanups - please read.)
Posted by Chuck Rolke <cr...@redhat.com>.
Not to forget that the WCF project also links to qpidclient. Would the proposed changes retire WCF as well?
-Chuck
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org