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" <> 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.
>, +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:
API updates via Twitter:
Issues/Enhancements Tracker:
Change your membership to this group:

Reply via email to