Thanks you all .......Actually the problem with the API which I am using to get the target mobile time. The API always returns local time when I change it to GMT ....The things are fine in target.
Thanks once again for this timely help on Time... On Sep 2, 4:45 am, "Andrew W. Donoho" <andrew.don...@gmail.com> wrote: > On Sep 1, 2010, at 15:55 , M. Edward (Ed) Borasky wrote: > > > That's a surprise - I'd expect Apple to be on top of stuff like that! Even > > so, 18 seconds is well within Twitter's outrageously generous tolerance of > > five minutes. > > There are different sync. points for different devices. For example, iPhones > sync with AT&T. iPads sync with Apple. There appears to be a ≈30 second > difference between them. While being far from a time sync expert, I suspect > leap seconds are the issue. > > Anon, > Andrew > ____________________________________ > Andrew W. Donoho > Donoho Design Group, L.L.C. > a...@ddg.com, +1 (512) 750-7596 > > "We did not come to fear the future. > We came here to shape it." > > -- President Barack Obama, Sept. 2009 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en