Unifying service interfaces

  • [アーティクル]

As David Treadwell announced yesterday, we are starting to align the Windows Live services interfaces to use the AtomPub protocol, and to have a uniform set of conventions that are shared across internet services and the Project Astoria bits.

What does that mean? It means that starting now (and more in the future) you can interact with many consumer and infrastructure services in the same way. It also means that those Microsoft services out there and your own services -online or on-premises- created with the ADO.NET Data Services Framework look and behave in highly compatible ways.

You won't need to learn yet another API every time a new service comes out. Furthermore, we (or you, or services providers out there) won't need to create new APIs for every service. Highly uniform interfaces bring the opportunity for extensive client library and tools re-use across services of broad nature.

We've been talking about this for a while...and it's exiting to see the first pieces start to come in place.

If you want to know more, see live demos of services and tools working together, and chat about the details, we'll be going through all of this at Mix 2008. There is a talk specifically about this called "Accessing Windows Live Services using AtomPub" where I'll be telling the whole story and showing the thing working live.

More details about our Mix sessions here.

-pablo

Comments

  • Anonymous
    February 29, 2008
    Hey Pablo, I said the same yesterday: http://blogs.conchango.com/jamiethomson/archive/2008/02/28/windows-live-dev-announcements.aspx Standardisation on AtomPUB for Astoria and WL Services is a HUGE announcement. Fantastic news for developers. What I'm most exicted about is that WL Services can now be consumed using the client libraries that you guys already provide. Wow. -Jamie

  • Anonymous
    March 23, 2008
    The comment has been removed

  • Anonymous
    April 15, 2009
    I have three seperate tables loaded into my silverlight 2.0 c# program. Table A is loaded first. Table B is loaded Second. Table C is loaded Third. I am using the exact logic for updating, inserting and deleteing that is found in the Silverlight 2 ADO Documentation. If I update Table C, everything works. If I update table A or B I get the tracking error. If I switch the order, loadinding table B last, which makes it the most current table. The updating works just fine. Then, if I try to update table C, I get the tracking error. How do I establing the tracking, in the code, so I can update any or all three of the tables? Thank You