[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-191818-105":3,"detail-sidebar-cat-1-en-105":81,"doc-detail-191818-en":127},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","introduction-peer-to-peer-replication-in-winfs","Introduction - Peer-to-Peer Replication in WinFS","","WinFS Sync is a peer-to-peer, knowledge-driven, state-based replication service built for Microsoft Windows’ WinFS storage platform. It enables sharing, high availability, and offline access across environments ranging from home devices to globally distributed thousands of servers. Updates are exchanged lazily using pair-wise synchronization without locking and with minimal, scalable replication metadata. The protocol detects conflicting concurrent updates, supports automatic resolution, allows arbitrary synchronization topologies, supports disconnected operation, and guarantees eventual convergence.",{"@graph":14,"@context":73},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/template/","Template",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/template/presentations/","Presentations",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/introduction-peer-to-peer-replication-in-winfs/191818/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/introduction-peer-to-peer-replication-in-winfs/191818.png","ImageObject",442,249,{"name":42,"@type":43},"Pentious","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/octet-stream","2026-09-29","2026-09-03",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",9,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"What is WinFS Sync designed to do?","Question",{"text":63,"@type":64},"WinFS Sync is a replicated data service for WinFS that supports sharing information across machines and improving availability, including offline access. It is targeted at a broad class of applications.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"How does the replication protocol work at a high level?",{"text":68,"@type":64},"The protocol is peer-to-peer, knowledge-driven, and state-based. Machines exchange summaries of updates they know and synchronize items using local database state rather than a write log.",{"name":70,"@type":61,"acceptedAnswer":71},"What requirements does the protocol aim to satisfy?",{"text":72,"@type":64},"It operates on WinFS items, supports disconnected operation, uses minimal metadata, sends each update version at most once, detects conflicting versions for automatic resolution or logging, scales to large replica communities, and guarantees eventual convergence.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},191818,1788410970,{"code":4,"msg":82,"data":83},"success",[84,88,93,98,103,108,113,118,123],{"id":85,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":86,"slug":87},11,90,"presentations",{"id":89,"doc_module":22,"doc_module_name":25,"category_name":90,"show_sort_weight":91,"slug":92},12,"Resumes",80,"resumes",{"id":94,"doc_module":22,"doc_module_name":25,"category_name":95,"show_sort_weight":96,"slug":97},14,"Invoices",70,"invoices",{"id":99,"doc_module":22,"doc_module_name":25,"category_name":100,"show_sort_weight":101,"slug":102},15,"Posters",60,"posters",{"id":104,"doc_module":22,"doc_module_name":25,"category_name":105,"show_sort_weight":106,"slug":107},16,"Social Media",50,"social-media",{"id":109,"doc_module":22,"doc_module_name":25,"category_name":110,"show_sort_weight":111,"slug":112},17,"Forms",40,"forms",{"id":114,"doc_module":22,"doc_module_name":25,"category_name":115,"show_sort_weight":116,"slug":117},18,"Letters",30,"letters",{"id":119,"doc_module":22,"doc_module_name":25,"category_name":120,"show_sort_weight":121,"slug":122},21,"Paper Templates",5,"papers-templates",{"id":124,"doc_module":22,"doc_module_name":25,"category_name":125,"show_sort_weight":4,"slug":126},158,"General","general-158",{"code":4,"msg":82,"data":128},{"doc_id":79,"user_id":129,"nickname":42,"user_avatar":130,"doc_module":22,"category_id":85,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":109,"language":136,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":12,"update_tm":80,"read_time":140},1374404730887,"https://ap-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8","Peer-to-Peer Replication in WinFS\nLev Novik, Irena Hudis, Douglas B. Terry, Sanjay Anand, \u000bVivek J. Jhaveri, Ashish Shah, and Yunxin Wu\nMicrosoft Corporation\nABSTRACT\nWinFS, Microsoft’s new application storage platform, incorporates a novel peer-to-peer, knowledge-driven, state-based replication protocol.  The goal is to support diverse applications requiring replication for easy sharing, high availability, and offline access.  The system was designed to scale from a handful of personal computing devices in a home environment to thousands of servers that are globally distributed.  Like other weakly consistent replicated systems, the WinFS replication model allows update operations to be performed on any machine without locking.  Updated data items are sent between replicas in a lazy fashion via a pair-wise synchronization protocol.  The technical contributions of the protocol’s design include minimizing replication-specific state and efficiently propagating updates while allowing arbitrary synchronization topologies, detecting conflicting updates, supporting automatic conflict resolution, accommodating overlapping user communities, and guaranteeing eventual convergence.\nIntroduction\nWinFS Sync is a replicated data service designed to support the needs of a broad class of applications.  This replication protocol has been developed as part of a new storage system for Microsoft Windows called WinFS.  Replication serves the dual purpose of facilitating the sharing of information across machines and increasing the availability of that information.  For example, WinFS permits sales representatives to carry copies of a shared customer relationship database on their individual laptops, update data items while on the road, and later upload their updates to a server machine in the office or directly share updated items with their coworkers over a wireless network.\nThe WinFS replication protocol is characterized as peer-to-peer, knowledge-driven, and state-based.  Peer-to-peer means that the protocol allows pairs of machines to synchronize updates independently, thereby sending updated items through an application-specific overlay network.  Knowledge-driven means that sites maintain and exchange summaries of the updates they know, and sites use this information when deciding what items to send during synchronization.  State-based means that sites send updated items from their local databases rather than the sequence of operations that produced those items; the protocol does not rely on a write log but instead utilizes a small amount of metadata associated with each database entry.  The protocol achieves robustness through its knowledge-driven design, flexibility from a peer-to-peer model, and scalability by conserving network bandwidth and maintaining minimal metadata.  This paper presents the first replication system that combines these three properties to meet the following demanding design goals:\nOperate on WinFS items.  Any data item can be replicated on any machine running WinFS.\nSupport disconnected operation.  Data items may be replicated on machines that have intermittent network access, such as laptops and other mobile devices.\nRely on minimal metadata.  The information used to drive the replication process must be proportional to the size of the database and not grow with the update rate.\nDeliver updates at most once.  Once a replica receives a given version of an item, it should not be sent that version again.\nDetect conflicting versions.  Concurrent updates to an item must be detected and either resolved automatically or logged for manual resolution.\nScale to thousands of replicas.  Communities of 5,000 read-write replicas and 100,000 read-only replicas must be supported.\nGuarantee eventual convergence.  All sites that share replicated data must eventually receive all updated data items and agree on the latest version of each item.\nThese requirements and the motivation behind them are discussed in more detail in the following","cbCaiecp9TcPJj4H","https://ap.wps.com/l/cbCaiecp9TcPJj4H","doc",1404928,"English","# Introduction\n## WinFS Sync and replication goals\n## Replication requirements\n## Protocol characteristics and design contributions\n## Paper structure overview","[{\"question\":\"What is WinFS Sync designed to do?\",\"answer\":\"WinFS Sync is a replicated data service for WinFS that supports sharing information across machines and improving availability, including offline access. It is targeted at a broad class of applications.\"},{\"question\":\"How does the replication protocol work at a high level?\",\"answer\":\"The protocol is peer-to-peer, knowledge-driven, and state-based. Machines exchange summaries of updates they know and synchronize items using local database state rather than a write log.\"},{\"question\":\"What requirements does the protocol aim to satisfy?\",\"answer\":\"It operates on WinFS items, supports disconnected operation, uses minimal metadata, sends each update version at most once, detects conflicting versions for automatic resolution or logging, scales to large replica communities, and guarantees eventual convergence.\"}]","Introduction - Peer-to-Peer Replication in WinFS | DOC",6]