I'd also suggest the patch I made w/ QPID-1904 - The C++ AbsTime & Duration values are not set to a consistent epoch, which causes problems when you try using QMF timestamps across Linux and Windows, and even on Windows when you try and talk between Python and C++ clients. I submitted a patch which forces the epoch to that specified in AMQP, instead of inheriting it from the platform, which seems quite wrong for a network protocol across platforms with differing native epochs. The epoch is calculated once, and the conversion was already relative to a base, so there should be no performance hit.
On Thu, Apr 22, 2010 at 8:27 AM, Emmanuel Bourg <ebo...@apache.org> wrote: > Rajith Attapattu a écrit : >> >> I have taken care of QPID-2508 and QPID-2522 from Emmanuel. >> I left the MINA patch to Martin as he is more familiar with that side. > > Thanks all for taking care of the patches. There is also an involved patch > waiting for a thorough review in QPID-2433. > > https://issues.apache.org/jira/browse/QPID-2433 > > Emmanuel Bourg > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org