A framework for consistent, replicated Web objects

A.M. Kermarrec, I. Kuz, M. van Steen, A.S. Tanenbaum

Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

23 Citations (Scopus)

Abstract

Despite the extensive use of caching techniques, the Web is overloaded. While the caching techniques currently used help some, it would be better to use different caching and replication strategies for different Web pages, depending on their characteristics. We propose a framework in which such strategies can be devised independently per Web document. A Web document is constructed as a worldwide, scalable distributed Web object. Depending on the coherence requirements for that document, the most appropriate caching or replication strategy can subsequently be implemented and encapsulated by the Web object. Coherence requirements are formulated from two different perspectives: that of the Web object, and that of clients using the Web object. We have developed a prototype in Java to demonstrate the feasibility of implementing different strategies for different Web objects.

Original languageEnglish
Title of host publicationProceedings 18th International Conference on Distributed Computing Systems 1998
Place of PublicationPiscataway, NJ
PublisherIEEE
Pages276-284
Number of pages9
ISBN (Print)0-8186-8292-2
DOIs
Publication statusPublished - 1 May 1998
Externally publishedYes
Event18th IEEE International Conference on Distributed Computing Systems, ICDCS 1998 - Amsterdam, Netherlands
Duration: 26 May 199829 May 1998
Conference number: 18

Publication series

NameProceedings International Conference on Distributed Computing Systems
PublisherIEEE
Volume1998
ISSN (Print)1063-6927

Conference

Conference18th IEEE International Conference on Distributed Computing Systems, ICDCS 1998
Abbreviated titleICDCS
CountryNetherlands
CityAmsterdam
Period26/05/9829/05/98

Fingerprint

Dive into the research topics of 'A framework for consistent, replicated Web objects'. Together they form a unique fingerprint.

Cite this