000 04528nam a2200697 i 4500
001 6813180
003 IEEE
005 20200413152851.0
006 m eo d
007 cr bn |||m|||a
008 081006s2008 cau fob 000 0 eng d
020 _a159829203X (electronic bk.)
020 _a9781598292039 (electronic bk.)
020 _z1598292021 (pbk.)
020 _z9781598292022 (pbk.)
024 7 _a10.2200/S00132ED1V01Y200807MPC005
_2doi
035 _a(OCoLC)228154516
035 _a(CaBNVSL)gtp00531493
040 _aCaBNVSL
_cCaBNVSL
_dCaBNVSL
050 4 _aQA76.59
_b.T47 2008
082 0 4 _a004.165
_222
100 1 _aTerry, Douglas B.
_q(Douglas Brian)
245 1 0 _aReplicated data management for mobile computing
_h[electronic resource] /
_cDouglas B. Terry.
260 _aSan Rafael, Calif. (1537 Fourth Street, San Rafael, CA 94901 USA) :
_bMorgan & Claypool Publishers,
_cc2008.
300 _a1 electronic document (xi, 93 p.) :
_bdigital file.
490 1 _aSynthesis lectures on mobile and pervasive computing ;
_v#5
538 _aMode of access: World Wide Web.
538 _aSystem requirements: PDF reader.
500 _aPart of: Synthesis digital library of engineering and computer science.
500 _aSeries from website.
504 _aIncludes bibliographical references (p. 83-91).
505 0 _aIntroduction -- System models -- Data consistency -- Replicated data protocols -- Partial replication -- Conflict management -- Case studies -- Conclusions -- Bibliography.
506 1 _aAbstract freely available; full-text restricted to subscribers or individual document purchasers.
510 0 _aCompendex
510 0 _aGoogle book search
510 0 _aGoogle scholar
510 0 _aINSPEC
520 0 _aManaging data in a mobile computing environment invariably involves caching or replication. In many cases, a mobile device has access only to data that is stored locally, and much of that data arrives via replication from other devices, PCs, and services. Given portable devices with limited resources, weak or intermittent connectivity, and security vulnerabilities, data replication serves to increase availability, reduce communication costs, foster sharing, and enhance survivability of critical information. Mobile systems have employed a variety of distributed architectures from client-server caching to peer-to-peer replication. Such systems generally provide weak consistency models in which read and update operations can be performed at any replica without coordination with other devices. The design of a replication protocol then centers on issues of how to record, propagate, order, and filter updates. Some protocols utilize operation logs, whereas others replicate state. Systems might provide best-effort delivery, using gossip protocols or multicast, or guarantee eventual consistency for arbitrary communication patterns, using recently developed pairwise, knowledge-driven protocols. Additionally, systems must detect and resolve the conflicts that arise from concurrent updates using techniques ranging from version vectors to read-write dependency checks. This lecture explores the choices faced in designing a replication protocol, with particular emphasis on meeting the needs of mobile applications. It presents the inherent trade-offs and implicit assumptions in alternative designs. The discussion is grounded by including case studies of research and commercial systems including Coda, Ficus, Bayou, Sybase's iAnywhere, and Microsoft's Sync Framework.
530 _aAvailable also in print.
588 _aTitle from PDF t.p. (viewed on Oct. 10, 2008).
650 0 _aCache memory.
650 0 _aData transmission systems.
650 0 _aDatabase management.
650 0 _aMobile computing.
650 0 _aUbiquitous computing.
690 _aMobile data management.
690 _aReplication.
690 _aCaching.
690 _aMobility.
690 _aUbiquitous computing.
690 _aDisconnected operation.
690 _aIntermittent connectivity.
690 _aData consistency.
690 _aConflict detection.
690 _aUpdate propagation.
690 _aEpidemic algorithms.
710 2 _aMorgan & Claypool Publishers.
730 0 _aSynthesis digital library of engineering and computer science.
830 0 _aSynthesis lectures in mobile and pervasive computing ;
_v#5.
856 4 2 _3Abstract with links to resource
_uhttp://ieeexplore.ieee.org/servlet/opac?bknumber=6813180
999 _c561626
_d561626