Live mesh & live framework

Editor's Notes

• #3: rise of “social computing”, intrinsic to the user’s data is the notion of sharing
• #4: Hard to manage data, devices, people, apps -> Framework to solve problem -> connecting devices, data & apps through a consistent, approachable framework The notion of “my computer” -> a user’s “mesh-- where a mesh is the sum total of a user’s data and data shared with the user’s friends and family, all stored on a set of related devices (including cloud devices).
• #5: Client & Desktop built on top of Live fx, no hidden API’s Client supports: PC (XP, Vista) Mac Windows Mobile 6
• #6: General picture: MS Vision of Cloud Computing Windows Azure as Cloud OS Services on the cloud to support their applications and allow us to make applications
• #7: Live Services: Identity services: manage person, device & app identities with associated services like Delegate Authentication -> at center of everything (Live ID, sign-in/up, app key management, ...) Directory services: manage association & relationships between identities, data, devices & apps Storage: manage persistence and retention of user-centric info as contacts, files and extensible data types Communication & presence services: provide transport infrastructure for transient & persistent state management between apps & devices Search: set of technologies for building/enhancing search on websites & apps Geospatial: geocoding/reverse geocoding features, routing, search, road/aerial image mapping for visualizing geospatial data Mesh services = underlying core services of Live fx (added/targetted for the mesh) Users: managing a user’s Mesh (dev, app, data) + sharing these resources across multiple users. Devices: managing collection of dev (including relationships, status, security, ...) in a user’s Mesh Application Management Services facilitate configuration, deployment and versioning of apps (including Mesh apps) Synchronization: ensure a seamless synchronization of data and metadata between apps, devices & the cloud (open protocols)
• #8: Live Operating Environment Symmetric Cloud & Client Service Composition Engine Integrated Synchronization & offline operations Communications, device management, presence & notification services The HTTP Endpoint can be accessed using protocols such as Atom Pub, JSON, RSS, etc Resource Model Served from the Live Framework runtime environment. (Live Operating Environment) Core Services like Identity, Devices and applications. Specific user data: Photos, files, contacts, calendar events Communication Infrastructure: Device to device or application to application communication and synchronization Application Model: To help you distribute your applications Library Entry points into the Live Framework using API kits. .NET, Silverlight and JavaScript
• #9: = User-centric data store API = REST Model = Feeds (rss/atom) Set of Properties (relationships, type, ...) + Entity (resource) + Collection of new entities Resource Model: This consists of user resources and relationships between resources. Each resource exposes specific user information such as Contacts, Profiles, Mesh Objects, Devices, and News, and they are all represented in terms of URL addressable endpoints. These resources can be projected to various type systems. Data Entry Base unit of extensible storage. Think of it as an item in the grocery list, or a blob Multiple data entries can loosely associate together Media related: in MediaResources Data Feed Collection of Data Entries, unit of synchronization Things are the same level: Members: Who is this data being shared with and what role do they have Mappings: Which devices does this data appear on. Both users and applications can select that News: What events are happening, user or application generated Subscription: What events are happening to this mesh object Mesh Objects Container for data that is replicated across devices Also a unit of permissioning Mesh (owned/controlled by user) This is the Mesh Resource Under it are: All the devices in the Mesh: A MeshDeviceResource represents a physical device claimed by a user. All the Applications in the Mesh: The ApplicationResource represents a provisioned and registered application entity in the application catalog. The ApplicationResource optionally contains a packaged form of the application binaries. All the mesh objects in the Mesh: A MeshObjectResource is the container for user-defined metadata. The MeshObjectResource is a fundamental unit of extensibility, sharing, and synchronization. The resource can be replicated across a set of devices and shared among a set of identities. All the News happening in the Mesh: NewsItemResource resources represent user news streams. A NewsItemResource is a collection of aggregated news items corresponding to the activities across the user’s MeshResource resources, spanning all federated storage service instances, members, and devices. Each news item is a unit of publication and subscription. All the events occurring in the Mesh: A NotificationQueueResource contains notifications associated with resources. A pointer to the notification queue is added as part of the subscription to a particular resource. Notification queues are polled by client applications to get updates on the resource.
• #10: Very usefull to LEARN + Debug
• #11: Winform/WPF/ASP.NET/MVC -> .NET 3.5 FX API library Silverlight -> Silverlight API 3rd Party -> Javascript library Examples: Live Mesh Client = 3.5 Live Mesh Destkop = Javascript