Windows Live takes a 180degree about turn with APP adoption
[This blog entry might be a bit techie. Bear with me.]
Take a read of the following two quotes:
"…we [Microsoft] couldn’t figure out how to use APP without putting an unacceptable implementation and performance burden on both our customers and ourselves. So we felt we had no other option [but to invent Web3S]. But Web3S is a tactical not a strategic choice. If it turns out there is a better option then we’ll adopt it." – Taken from APP and Dare, The Sitting Duck by Yaron Goland, 15th June 2007"Microsoft is making a large investment in unifying our developer platform protocols for services on the open, standards-based Atom format (RFC 4287) and the Atom Publishing Protocol " – Taken from David Treadwell on New and Updated Windows Live Platform Services, 27th February 2008
N.B. APP stands for Atom Publishing Protocol
So back in June Microsoft said a resounding "No" to APP yet just over 8 months later they decide that actually yes, APP is the basket into which all their eggs are being placed. I have nothing against people changing their minds about decisions like this, I do it all the time in my day job, but at the time of writing that hasn’t really been any explanation as to the rationale for that decision nor what pains the Windows Live team went through in making it. I keep hoping that Yaron will elucidate on this but he hasn’t done as yet.
I have said before that protocol standardisation is a good thing but I can’t help but be perturbed by some of the issues that Yaron raised in his blog entry, mainly around the use of optimistic concurrency when merging data. The problem scenario that Yaron describes (where 2 updates to the same entity can result in an erroneous race condition) is a very real one and I would like to know how the Windows Live folks are going to prevent that problem from occuring.