You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "james strachan (JIRA)" <ji...@apache.org> on 2006/10/18 13:50:16 UTC
[jira] Assigned: (AMQ-971) NMSTimestamp returning LocalTime instead
of UTC
[ https://issues.apache.org/activemq/browse/AMQ-971?page=all ]
james strachan reassigned AMQ-971:
----------------------------------
Assignee: Hiram Chirino
> NMSTimestamp returning LocalTime instead of UTC
> -----------------------------------------------
>
> Key: AMQ-971
> URL: https://issues.apache.org/activemq/browse/AMQ-971
> Project: ActiveMQ
> Issue Type: Improvement
> Components: NMS (C# client)
> Affects Versions: incubation
> Environment: Windows
> Reporter: Rob Lugt
> Assigned To: Hiram Chirino
> Priority: Minor
>
> The NMSTimestamp property has been changed from long to DateTime - which is a good thing. However, the DateTime is currently being adjusted to localtime before being returned to the client - which is probably not ideal. The DateTime struct does not contain timezone information, therefore the programmer has to make some assumption about what timezone the time is expressed in. A UTC time is more in-keeping with the JMS specification - which specifies that Timestamp is a normal Java time i.e. expressed in GMT. This article from Microsoft also suggests using UTC as a common time where possible: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/datetimecode.asp
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira