Channel9のインタビューのTranscriptが出てた。(゜∀゜)
ttp://perspectives.on10.net/blogs/jonudell/Ray-Ozzie-introduces-Live-Mesh/

重要な部分をピックアップ。


The base model of what is an application within the Live Mesh environment begins with
essentially a feed of feeds. One feed represents a logical thing that a site might be exchanging
with the client. That's called a mesh object. It's a feed of feeds. A developer can new up
one of these things, and its elements are other feeds. An application can develop as many
feeds as it likes. Some of those feeds are hard-wired to be things like the list of members,
or the list of devices in the feed, but then the application can develop many more.


In what they see today, if you open up a folder, what we would refer to as a mesh-enabled folder
-- it's one of these mesh objects. And in essence every file within that folder is an element,
it as an item within the feed. The file itself is the enclosure. The metadata of the file -- its name,
its modified date and so on -- are a standard schema that represents the item. Then there's
a news feed that you'll see on the right hand side if you open up one of these folders, that's
another feed, and each of the entries in there is another item, and so on.


We made a decision, from an API perspective, that developers would prefer to learn one way
of dealing with the mesh, and that the tooling would be easier if we had one way of dealing with
the mesh. So the web version of Live Mesh, what's running up in the web, and what's running on
the client, are symmetrical and the same code. So on localhost, in a secure way, an application
uses REST calls to invoke -- we call it MOE, the mesh operating environment -- or it calls
cloud MOE to do what it needs to do.