Linked by Thom Holwerda on Wed 2nd Jan 2013 23:38 UTC
Microsoft Microsoft's legal chief: "We continue to be dogged by an issue we had hoped would be resolved by now: Google continues to prevent Microsoft from offering consumers a fully featured YouTube app for the Windows Phone." Utter nonsense, since MetroTube offers a complete and full YouTube experience on Windows Phone (it's one of the best Windows Phone applications), and YouTube+ on Windows 8. Two fantastically rich applications, built by small ISVs - yet Microsoft can't do the same? Don't make me laugh. Coincidentally, Microsoft is also whining some more about Google's removal of ActiveSync - Redmond again refuses to acknowledge that all it needs to do is implement the open standards CalDAV and CardDAV, just like everyone else has done. Times have changed, Ballmer. You don't get to dictate the industry anymore.
Permalink for comment 547143
To read all comments associated with this story, please click here.
RE[2]: DAV
by telns on Thu 3rd Jan 2013 22:08 UTC in reply to "RE: DAV"
telns
Member since:
2009-06-18

The first barrier is that there is no equivalent industry-wide "DAV" for e-mail. I'll actually ignore that, though, as at least in theory one could develop.

For mobile sync, the primary focus will be on efficiency and prompt change notification. Dedicated sync protocols can do this fairly well, and aggregate all the data types (email, calendar, contacts, tasks) into a single point, delivering changes to them in near real-time and minimizing the number of open connections required on the phone (important for battery life). The integration is key, because some of these are more closely related than you'd think. I get an e-mail invitation, which needs added to my calendar--and my free/busy index updates so other people can see I'm booked--and then I do a search in my company contact's directory to add another attendee.

That tight integration is missing in the DAVs, as is any standardized method of "pushing" changes.

Another big one is the fact that now I have all this important mail, calendar, and contact data on my phone, what if I lose it? What if my company wants to make sure I use a PIN? Sync protocols usually include extra commands to provision the phone according to company policies for encryption and passwords, allow remote wipe, &c.

DAV is great as an API, but to turn it into a sync protocol, you really need some kind of shim in between that trims it all down, aggregates the data sources, simplifies change notification, and provides just the subset of functionality needed on mobile devices, while adding in specific new capabilities like remote wipe. When people feel like getting super fancy, that can also add mobile enhancements like sending only the new text in a reply or a forward, pulling in the original text on-the-fly, and other such niceties.

But by the time you've done all that, it no longer looks like plain-vanilla DAV.

Edited 2013-01-03 22:14 UTC

Reply Parent Score: 1