John Mcintyre started by showing a picture of the Live Framework and the part of it where his talk is about.

The connected experience is about user expectations of integrated experiences that span devices, applications and browser-rich clients.
It also has to face the enginering reality of that even simple scenarios are difficult to implement, lots of infrastructure is required to get it of the ground.
The result for the user is that devices, applications and services create islands on which the user must survive.

How does the user get off that island? Services and devices must be working together to deliver connected experiences by unlocking data for anywhere access, by lighting up devices with consistent capabilities and connect data and devices through services.
So connectivity and communcation is the key by closing the gaps between data and devices and by delivering relevant information to enliven experiences.
Communication Services is able to connect devices, data and users through a consistent, approachable framework.

Communication Services powers connected experiences.
It enables connected data by using subscription and change notification services.
It enables connected devices by using an overlay of communication network and peer-to-peer.
It enables connected users by using awareness and activity services

Subscriptions and Notifications should be simple, scalable and resilient.

In order to get connected data a user must subscribe to a resource for a particular device. LiveFX supplies methods for that which get passed through to a Resource Manager. The Resource Manager subscribes to a Subscribtion Service. These services fanout to the Queue Services. When a resource is queued that has a subscription it gets transported to LiveFX which delivers it to the device associated with the subscription.

Notification scale is achieved by horizontal scaling through partinioning and instance management, consistent hashing for resource addressing and all is stored as in-memory tables, TTLs enforced
There are two failure modes: state loss when subscription instances go down and queue loss when queue service instances go down. In both cases the notification service will alert and recover.

Connected devices use peer-to-peer communications which should be seamless, secure and reliable.

Activity and News services are used to get users connected.
Ativities are used to supply a high performance for transient state consisting of presence information. Publishers should also subcribe too which implies possible state loss.
News services are used to supply durable “news worthy” state or state change.

One final slide to wrap it all up.