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 2011/11/17 17:57:57 UTC
Request to include QPID-3626 in 0.14
Hi Justin,
Would it be possible to include the fix for QPID-3626 in the upcoming rc?
https://issues.apache.org/jira/browse/QPID-3626
Without it, any python client that would like to access the timestamp would have to revert to using the old client API, something we don't want to encourage going forward.
thanks,
-K
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Request to include QPID-3626 in 0.14
Posted by Ken Giusti <kg...@redhat.com>.
Rajith +1 -K
----- Original Message -----
> On Thu, Nov 17, 2011 at 12:03 PM, Gordon Sim <gs...@redhat.com> wrote:
> > On 11/17/2011 04:57 PM, Ken Giusti wrote:
> >>
> >> Hi Justin,
> >>
> >> Would it be possible to include the fix for QPID-3626 in the
> >> upcoming rc?
> >>
> >> https://issues.apache.org/jira/browse/QPID-3626
> >>
> >> Without it, any python client that would like to access the
> >> timestamp
> >> would have to revert to using the old client API, something we
> >> don't want to
> >> encourage going forward.
> >
> > I'm in favour of this as (a) it helps keep the messaging API
> > clients
> > consistent rather than letting them diverge and (b) it is very low
> > risk.
>
> I'm fine with this change as well.
> However I'm not too keen to introduce the change in the JMS client to
> use a custom property to carry the JMS timestamp for this particular
> release. There is some evidence that the increase in message
> properties have an adverse impact on performance.
>
> However we should include the change in the JMS client for the next
> release and hopefully we would have a chance to address the perf
> issue
> related to message properties.
>
> Regards,
>
> Rajith
>
> > ---------------------------------------------------------------------
> > Apache Qpid - AMQP Messaging Implementation
> > Project: http://qpid.apache.org
> > Use/Interact: mailto:dev-subscribe@qpid.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Request to include QPID-3626 in 0.14
Posted by Rajith Attapattu <ra...@gmail.com>.
On Thu, Nov 17, 2011 at 12:03 PM, Gordon Sim <gs...@redhat.com> wrote:
> On 11/17/2011 04:57 PM, Ken Giusti wrote:
>>
>> Hi Justin,
>>
>> Would it be possible to include the fix for QPID-3626 in the upcoming rc?
>>
>> https://issues.apache.org/jira/browse/QPID-3626
>>
>> Without it, any python client that would like to access the timestamp
>> would have to revert to using the old client API, something we don't want to
>> encourage going forward.
>
> I'm in favour of this as (a) it helps keep the messaging API clients
> consistent rather than letting them diverge and (b) it is very low risk.
I'm fine with this change as well.
However I'm not too keen to introduce the change in the JMS client to
use a custom property to carry the JMS timestamp for this particular
release. There is some evidence that the increase in message
properties have an adverse impact on performance.
However we should include the change in the JMS client for the next
release and hopefully we would have a chance to address the perf issue
related to message properties.
Regards,
Rajith
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Request to include QPID-3626 in 0.14
Posted by Gordon Sim <gs...@redhat.com>.
On 11/17/2011 04:57 PM, Ken Giusti wrote:
> Hi Justin,
>
> Would it be possible to include the fix for QPID-3626 in the upcoming rc?
>
> https://issues.apache.org/jira/browse/QPID-3626
>
> Without it, any python client that would like to access the timestamp would have to revert to using the old client API, something we don't want to encourage going forward.
I'm in favour of this as (a) it helps keep the messaging API clients
consistent rather than letting them diverge and (b) it is very low risk.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org