Having problems with message search?
Pl see http://www.timeanddate.com/worldclock/converted.html?month=10&day=29&year=2009&hour=0&min=0&sec=0&p1=137&p2=220
-7:00 is California/Los Angeles (Server) time offset from GMT and -6:00 is Salt Lake City (Receiver) time offset from GMT. Time is correct. You need to adjust the zone lag (-7:00) and the time to your own time zone. Do not hard code -7:00 since you could be getting it from an East Coast server too.
See http://www.faqs.org/rfcs/rfc3339.html
Thx & Rgds
--Arnab
-7:00 is California/Los Angeles (Server) time offset from GMT and -6:00 is Salt Lake City (Receiver) time offset from GMT. Time is correct. You need to adjust the zone lag (-7:00) and the time to your own time zone. Do not hard code -7:00 since you could be getting it from an East Coast server too.
See http://www.faqs.org/rfcs/rfc3339.html
Thx & Rgds
--Arnab
From: cymant1x <robstefanussen@...>
To: fireeagle@yahoogroups.com
Sent: Thu, 29 October, 2009 7:13:10 AM
Subject: [fireeagle] Location updates being sent with the wrong timestamps?
We're experiencing an issue with location updates being sent with timestamps which are one hour earlier than they should be.
For example: If I set my location from fireeagle.yahoo. com to be Salt Lake City at 10:30 AM, the "located-at" timestamp will read something like this: 2009-10-28T09: 30:00-07: 00. Since SLC is in timezone "America/Denver, " the -07:00 is correct, but 09:30:00 is one hour too early.
Is this a bug in FireEagle? Could it have something to do with the fact that DST goes out of effect after this Sunday?
Now, send attachments up to 25MB with Yahoo! India Mail. Learn how.
Offline 
Send Email