Apple has that syncing feeling over MobileMe
When we say push, we really mean shove
Regcast training : Hyper-V 3.0, VM high availability and disaster recovery
Apple has rewritten marketing bumf for its MobileMe service after it emerged the "push" service actually needed customers to do their own share of shoving when it came to updating desktop apps.
MobileMe, or "Exchange for the rest of us" as Apple bills it, is supposed to push data between online storage, which Apple calls "The Cloud", desktop applications such as iCal, and mobile devices such as the iPhone or iPod Touch.
But while some data is being pushed and some being pulled, the rest is still reliant on a synchronisation process inherited from its ".mac" predecessor.
Email is managed through IMAP, and strictly speaking is pulled by polling the IMAP servers every minute, though that gives a reasonable impression of being pushed.
But the dispersal mechanism for updates to the contacts or calendar are dependent on where the changes are made. Updates made to The Cloud (through a web interface) are instantly pushed to the desktop applications and iPhones, and changes made on an iPhone (or iPod Touch) are echoed to The Cloud and desktop. But changes made using the desktop application are not instantly or automatically reflected on the iPhone or within The Cloud.
Such changes need to wait for a synchronisation process, a lag of up to 15 minutes, before they are propagated between the platforms. Not only that but anyone trying to use some of the more advanced IMAP capabilities, such as the APPEND command, will find the MobileMe service unaware that any changes have been made to their e-mail account, at least until a good-old SMTP delivery triggers notification.
To most people these might seem a minor issues, but many Mac users are up in arms about what they see as inaccurate representation of the service.
The vehemence is such that Apple has amended its descriptions to reflect the fact that desktop applications need to have a sync interval set up, as shown by a comparison hosted by MacRumours.
The issue is certainly being taken seriously by some, though. As one poster to the Apple discussion forum put it: "Pretty much the only reason I signed up for MobileMe was to be able to 'push' calendar and contact changes between my four Macs and two iPhones."
Quite why the poster feels the need to maintain six identical contact lists on four computers and two iPhones we don't know, but with such a spread of devices instant synchronisation is clearly a necessity and a 15-minute delay unacceptable. ®
Regcast training : Hyper-V 3.0, VM high availability and disaster recovery
COMMENTS
Apple Breaking RFC Mail spec?
I've also been affected by the 'downgrade' to me.com service. Since the launch of the 'ME' service on 7/16/08 my email from my @mac.com has been non-functional.
Email sent to my @mac.com DOES NOT BOUNCE like it should when an EMAIL SERVER IS _DOWN_.
http://www.lesnikowski.com/mail/Rfc/rfc2821.txt
So why is apple breaking RFC2821 and surpressing the delivery of 'UNDELIVERABLE' messages to people effected by their 'downgrade' <strike>'upgrade'</strike> in service?
I've been sending a few emails to my undeliverable_email@mac/me.com account and not a one of them since 7/16/08 have returned to me as 'UNDELIVERABLE'. Clearly, the service is down (for the 1% of how many millions of users?) for me. Clearly I should receive an email BACK as UNDELIVERED, shouldn't I? I believe there is a 5 day resend limit per RFC spec.
Why does Apple think it is in the users best interest to 'hold their mail' when senders to the Me/MacMail account never got a message back saying the message was undelivered?
I sure hope none of the users have anything critical they need to get access to like banking or other related billing messages..... of course they don't!
:(
A.C.
Old school
Seems is type of tech is nothing new. From what I can gather, the service is build on top of MS Exchange's 'push' service, which in turn is a spin-off of the crackberry.
http://technet.microsoft.com/en-us/library/aa997252(EXCHG.80).aspx
I love the use of the phrase "long-lived HTTPS request". Sound very much like the HTTP(s) counterpart to IMAP-IDLE.
http://tools.ietf.org/html/rfc2177
I just tried to register for the service
by typing www.me.com into the browser on my PC and it told me that I have to use Safari or Firefox. Given that I'm using a locked down work PC with Explorer, that effectively means I can't use it as I can't install either of the 2 browsers it asks for as I don't have sufficient admin rights and the IT outsourcer refuses to install additional browsers.
Looks like I won't be signing up for it..........

IT infrastructure monitoring strategies
Agentless Backup is Not a Myth
Steps to Take Before Choosing a Business Continuity Partner
Requirements Checklist for Choosing a Cloud Backup and Recovery Service Provider
Data control in the cloud