|
||||
Re: Direct Push is really not Direct Push
Direct push uses http requests that stay unanswered for a long time and self tunes to the optimal time on the device side. This can cause issues with routers where responses cannot be returned. This will bust direct push and cause it to behave like a polling system. It doesn't use UDP so far as I know.
|
|
||||
Re: Direct Push is really not Direct Push
Mine sometimes comes to my phone before my Desktop. Could be your Exhange Server.
|
|
||||
Re: Direct Push is really not Direct Push
Quote:
mine is the same.....I get the email on my phone 5-10 secs before my pc.
__________________
![]() ![]() |
|
||||
Re: Direct Push is really not Direct Push
Quote:
Ironically I have 2 co-workers with touches that also have latency like me. |
|
||||
Re: Direct Push is really not Direct Push
try going to programs->activesync->menu->schedule and verify that both "Peak times" and "Off-peak times" are set to "As items arrive."
|
|
||||
Re: Direct Push is really not Direct Push
well hey, i cant even figure out how to get corporate email to work on my touch.. and we have no tech support here
![]() |
|
||||
Re: Direct Push is really not Direct Push
Sorry to keep this off-topic, but I wanted to help Frank and other fellow Lotus Notes users.
http://web.commontime.com/
__________________
If you are new to the site, take a look at the PPCGeeks New User Guide to get an overview of how to use the forums.
Having problems finding what you're looking for? Here are some tips on how to search the site more effectively. |
|
||||
Re: Direct Push is really not Direct Push
I sometimes wonder if it's Sprint's network. Some days it hits my phone first, other days it hits my desktop first. I wish it were more consistent. With 6.0 it was. usually hit both desktop and phone at the same time and any changes I made on one, reflected on the other nearly instantly. Sadly, it's only been 6.1 that isn't consistant.
|
![]() |
|
|
|