An Open Platform?


Our mantra for designing the Live Mesh platform has been "comprehensive, simple, open."  We’ve released two more Channel 9 videos this week to show what we mean.

As far as comprehensive goes, check out Ori Amiga’s video showing off some sample apps and a peak at how the platform works under the covers.  Clients and services, online and offline, files and applications…it’s a pretty impressive set of demos to give some weight to our comprehensive claim.

When it comes to open and simple, you can see some of that in the demo where Ori browses through the resource model, starting around 11:40.  You see a RESTful model, you see feeds, you see ATOM, JSON and other formats, and you see FeedSync.  Which brings us to…another channel 9 video!

We got Steven Lees, one of the guys behind the FeedSync v1.0 spec, to sit down with the developer who built the Live Mesh client runtime that consumes/publishes FeedSync, plus the PM and dev who built the corresponding Live Mesh cloud storage service.  Have a look here.

Using FeedSync as the basis for synchronization is a key to making the platform open and accessible.  It was developed with community feedback, and is covered by Creative Commons ShareAlike and Microsoft Open Specification Promise.  Which enables folks to work on projects like Mesh4x.

 

– Jeremy Mazner

Program Manager (and blog oversight guy), Live Mesh

Technorati Tags:
Comments (6)

  1. Bryant Likes says:

    How about removing the UAC requirement on the client?

  2. jmazner says:

    @Bryant: see http://blogs.msdn.com/livemesh/archive/2008/04/28/get-mesh-and-why-we-require-uac.aspx for details on why UAC is required to be enabled for now (until we finish our own testing with Vista SP 1)

  3. Joel’s blog is one of the best resources on the net for software development. I find myself agreeing with him most of the times but his latest post on Live Mesh didn’t come out to be as insightful as some of his others.

  4. If you haven’t read Marc’s post go read it, then go read this post – all should be answered. With a mantra

  5. The MSDN Flash ( signup ) team in Australia let me write the editorial this month, below is what got