150 likes | 338 Vues
BB31. FeedSync And Live Mesh Sync Services. Steven Lees Program Manager Microsoft Corporation. FeedSync. Comprehensive. Simple. Open. Anywhere Access and Sharing. The Role Of Synchronization. Lots of ways to move data Why sync, why FeedSync ?. Anywhere Access: Requirements.
E N D
BB31 FeedSyncAnd Live Mesh Sync Services Steven Lees Program Manager Microsoft Corporation
FeedSync Comprehensive Simple Open
The Role Of Synchronization • Lots of ways to move data • Why sync, why FeedSync?
Anywhere Access: Requirements • Create new items anywhere • Universal ID • Efficient notification of deletions • Handle concurrent edits
Anywhere Access With Live Mesh your site FeedSync+HTTP HTTP to browser FeedSync+HTTP Live Mesh FeedSync+HTTP
API Choices • HTTP • FeedSyncClient/SyndicationClient • Live Framework • Sync Framework
You'll also want to know about… • Delegated authentication • Common data formats • Efficiency (incremental feeds) • Enclosures (file attachments) • Conflict resolution
Resources • FeedSync: • http://feedsync.org • (Look for session samples here soon…) • Microsoft Sync Framework: • http://msdn.microsoft.com/sync • Live Framework: • http://dev.live.com/liveframework • My blog • http://blogs.msdn.com/stevenlees
Related Sessions (Live Services) • BB04 - A Lap Around the Live Framework and Mesh • BB41 - What I Learned Building My First Mesh App • BB19 - Live Framework Architecture and Insights • BB51 - Programming Live Services Using Non-Microsoft Technologies • BB06 - Mesh Services Architecture • BB30 - Building Mesh-Enabled Web Apps • BB31 - FeedSync and Mesh Synchronization Services • BB35 - The Future of the Device Mesh • BB34 - Notifications, Awareness, and Communications
Evals & Recordings Please fill out your evaluation for this session at: This session will be available as a recording at: www.microsoftpdc.com
© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.