Any plans to fix the bug in Java client? (missing conversions between
seconds and milliseconds)
On Sep 15, 2011 7:21 PM, "Gordon Sim" <[email protected]> wrote:
> On 09/14/2011 05:46 PM, Jiri Krutil wrote:
>> My questions are:
>> - Why does the broker not set the message timestamp? (I thought the spec
>> says it should)
>
> I believe there was some concern over the performance impact. Since no
> one has previously raised a use-case for it, it hasn't really been
> investigated in great detail however.
>
> (
http://svn.apache.org/viewvc/incubator/qpid/trunk/qpid/cpp/src/qpid/broker/Message.cpp?r1=704211&r2=704210&pathrev=704211
)
>
>> - Why does the Java client set the timestamp fields to zero instead of
null,
>> if they are not set in the AMQP message?
>> - Why does not the Java client translate from seconds-since-epoch to
>> millis-since-epoch?
>> - Is any of these fixed in the latest version of the broker or Java
client?
>
> The broker still does not set the timestamp.
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:[email protected]
>
