activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <j...@apache.org>
Subject [jira] Moved: (AMQNET-28) NMSTimestamp returning LocalTime instead of UTC
Date Tue, 27 Feb 2007 10:39:06 GMT

     [ https://issues.apache.org/activemq/browse/AMQNET-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

james strachan moved AMQ-971 to AMQNET-28:
------------------------------------------

          Component/s:     (was: NMS (C# client))
    Affects Version/s:     (was: incubation)
                  Key: AMQNET-28  (was: AMQ-971)
              Project: ActiveMQ .Net  (was: ActiveMQ)

> NMSTimestamp returning LocalTime instead of UTC
> -----------------------------------------------
>
>                 Key: AMQNET-28
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-28
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>         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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message