Steven Lees started his talk with taking a picture with his mobile phone of the attendees of his session and let it be synchronised to his laptop on stage and the live desktop.

FeedSync should be comprehensive, simple and open.
It  comes down to you want Access Anywhere and Share Anything.

The role of synchronisation:
- there are lots of ways to move data
- so why Sync, why FeedSync

What are the requirements of Anywhere Access:

1. Create new items anywhere
2. Universal ID
3. Efficient notifications of deletions
4. Handle concurrent edits

They solved this by adding a sx:sync element to the feed message. It contains basicly version information regarding the message. Extra attributes handle things like deletion and concurrent edits.

Data from a phone gets synced with Live Mesh through FeedSync. From there the date can synced with a website or desktop computer also using FeedSync.

There are various choices for API use:
- HTTP
- FeedSyncClient / Syndication ….
- Live Framework
-

He ended with a few teasers you’ll want to know about …
- delegated authentication
- common data formats
- efficiency (incremental feeds)
- enclosures (file attachments)
- conflict reesolution