utc

I designed my application considering the fact that, according to the specifications, should run on a server located in Italy and clients will be italian people only. About a month ago, my bos decided to bring it all on Azure. Everything went smoothly. The only thing that give me some problem is the fact that the time server is UTC. The solutions are: A) simple modify a startup script to the server time ( http://netindonesia.net/blogs/wely/archive/2011/06/26/setting-timezone-in-windows-azure.aspx ) B) more laborious Change to make any application to use UTC and show the time properly converted

In my Mysql 5.0 DB I have a column to control LastUpdated information. The Column is a TimeStamp one and MySql automatic updates data. I'm trying to select this column in UTC format. The problem is that the server is setup to US datetime. According to MySql documentation, the DB stores the information in UTC but when I want to display information, it converts it to Server's time. Is there any way to do SELECT command avoiding this convertion? Besides changing the default timezone of the server, the timezone can also be adjusted per connection by executing this SQL statement: SET time_zone =

I'm facing some issue trying to use moment.js for dealing with time offsets. I collect in an hidden input the local user time offset: <script type="text/javascript"> $(document).ready(function () { $('input#timeoffset').val(moment().utcOffset()); }); </script> The offset gets correctly stored (in my case its value is -240). Later on the server side (which runs in utc time) I try to update some db stored utcDate doing something like: var userDate = moment(utcDate).utcOffset(offset) My issue is the following: if I run my code as above described I get no effects: utcDate: 20151001 012421 +0000

I'm trying to estimate a twitter user's location based on the time_zone or created_at value in a given tweet object. However it seems that all created_at values I've come across are just in a pointless localised time and the time zone they supply isn't in the most helpful format example tweet "created_at":"Thu Jun 02 14:41:24 +0000 2011" "time_zone":null OR "created_at":"Sun Jan 09 05:03:52 +0000 2011" "time_zone":"Mountain Time (US & Canada)" Both of these times aren't in UTC time and the time_zone isn't in any particular standard format with the rest of the world I'm probably coming across

(This is a question about the UI rather than the technology required to do it) What is the clearest way to display a time for events occurring in different timezones to a user? Does your "average" user understand UTC and timezones? We capture the local time and UTC offset and store it in the database (SQL 2008 DateTimeOffset) for events happening in different timezones. Users are also in a variety of timezones. I'll suggest a couple of answers below so they can be rated but I'd appreciate alternative suggestions. EDIT: I'd like to avoid displaying the time in the user's timezone. Users in

The examples for Cache.Add uses DateTime.Now.Add to compute the expiration, i.e. it passes: DateTime.Now.AddSeconds(60) as the value of the absoluteExpiration parameter. I'd have thought that computing it relative to DateTime.UtcNow would be more correct [as there is no ambiguity if Daylight Savings Time starts in the intervening time between now and the expiration point]. Before the introduction of DateTimeKind , I'd have guessed that there's some ugly hacks in the cache management to make it do something appropriate if the time was not a UTC time. In .NET 2.0 and later, I'm guessing that it