[rabbitmq-discuss] Age of message

[cw storm]

MK,

In order to use the timestamp of the message property, don't you have to
issue the "*setTimestamp
<http://www.rabbitmq.com/releases/rabbitmq-java-client/v3.1.3/rabbitmq-java-client-javadoc-3.1.3/com/rabbitmq/client/AMQP.BasicProperties.html#setTimestamp(java.util.Date)>"
to populate it? If so, isn't **setTimestamp
<http://www.rabbitmq.com/releases/rabbitmq-java-client/v3.1.3/rabbitmq-java-client-javadoc-3.1.3/com/rabbitmq/client/AMQP.BasicProperties.html#setTimestamp(java.util.Date)>
deprecated?*


On Fri, Mar 21, 2014 at 8:51 AM, Michael Klishin <mklishin at gopivotal.com>wrote:

>
> On 21 Mar 2014, at 16:46, cw storm <cwstorm at gmail.com> wrote:
>
> > So you're saying that the OS has to sync with the NTP server.  Once
> that's confirm, then the message property of "timestamp" can be use to
> compare to the local time on the client server, right?
>
> After that you still can get inaccurate times from some machines but the
> possibility
> of that is greatly reduced. Syncing over NTP happens periodically. For a
> lot of apps,
> syncing once every few hours is good enough.
>
> MK
>
> Software Engineer, Pivotal/RabbitMQ
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140324/86f83d4c/attachment.html>