A framework for shared applications with a replicated architecture

Berlage, Thomas; Genau, Andreas

doi:10.1145/168642.168668

Cited by 52 publications

(38 citation statements)

References 18 publications

(2 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Users can thus collaborate in different modes, ranging from very loose coupling (e.g. single-user applications) to extremely tight coupling (Berlage and Genau, 1993;Haake and Wilson, 1992). The degree of coupling may be customisable according to the COLLABORATIVE PROCESS that is being enforced during a user's session.…”

Section: The Pattern Languagementioning

confidence: 99%

Architectural patterns for collaborative applications

Avgeriou¹,

Tandler²

2006

IJCAT

View full text Add to dashboard Cite

Abstract:There is currently little reuse of either design or code in the development of collaborative applications. Though there are some application frameworks for this domain, they tend to be rather inflexible in the functionality they offer. This paper seeks to provide design reuse in the form of architectural patterns that focus on low-level horizontal issues: distribution, message exchange, functional decomposition, sharing data, concurrency and synchronisation. We base these patterns on a number of well-established patterns in the domain of distributed applications, concentrating on the specific issues that are encountered in the domain of collaborative applications. We also outline the relation between these low-level architectural patterns and the high-level functionality that collaborative applications offer. By codifying this knowledge and experience in the form of patterns, we hope for a wider support of low-level architectural design to the community of collaborative applications and thus a further advance of the field.

show abstract

Section: The Pattern Languagementioning

confidence: 99%

Architectural patterns for collaborative applications

Avgeriou¹,

Tandler²

2006

IJCAT

View full text Add to dashboard Cite

show abstract

“…GINA [2] takes an approach wholly different from any of the previous merge procedures. Instead of basing the merge procedure on differences between object versions, GINA bases the merge on the command histories it keeps.…”

Section: Collaboration Toolsmentioning

confidence: 99%

“…Tools for merging plain-text files include the UNIX diff3 tool, the RCS rcsmerge tool [11], and the fileresolve tool in Sun's Network Software Environment [1]. Research efforts include the work of Horwitz, Prins, and Reps with a program merging tool that detects an inconsistent merge through the use of program dependency graphs [6], and the GINA collaborative application framework [2], which allows users to merge revised versions by merging command histories. Work related to object merging includes the PREP flexible diff tool [9], which gives users flexibility in finding and pinpointing differences, and the concurrency control model of Ellis and Gibbs [4], which determines a consistent ordering of operations at all sites in a distributed collaborative environment by merging concurrent operations.…”

Section: Introductionmentioning

confidence: 99%

A flexible object merging framework

Munson

Dewan

1994

Proceedings of the 1994 ACM Conference on Computer Supported Cooperative Work - CSCW '94

View full text Add to dashboard Cite

The need to merge different versions of an object to a common state arises in collaborative computing due to several reasons including optimistic concurrency control, asynchronous coupling, and absence of access control. We have developed a flexible object merging framework that allows definition of the merge policy based on the particular application and the context of the collaborative activity. It performs automatic, semi-automatic, and interactive merges, supports semanticsdetermined merges, operates on objects with arbitrary structure and semantics, and allows fine-grained specification of merge policies. It is based on an existing collaborative applications framework and consists of a merge matrix, which defines merge functions and their parameters and allows definition of multiple merge policies, and a merge algorithm, which performs the merge based on the results computed by the merge functions. In conjunction with our framework we introduce a set of merge policies for several useful kinds of merges we have identified. This paper motivates the need for a general approach to merging, identifies some important merging issues, surveys previous research in merging, identifies a list of merge requirements, describes our merging framework and illustrates it with examples, and evaluates the framework with respect to the requirements and other research efforts in merging objects.

show abstract

“…Also applies to objects who have new sub-objects set in a shared slot. .Other directions that we might take PERSON include sending command objects to support network undo as a concurrency control mechanism, as GINA [1] does, or making our naming scheme hierarchical.…”

Section: Future Workmentioning

confidence: 99%

Distributed applications

Bakht¹

1993

The MOSIX Distributed Operating System

View full text Add to dashboard Cite

This paper presents our experiences in implementing PERSON, a toolkit for adapting single user applications into multi-machine multi-user applications. This is achieved by providing a way to share objects in a peer-topeer model using a programming model that emphasizes values rather than functions and ties the values together with constraints.This encourages a modular and declarative style of program design.

show abstract

A framework for shared applications with a replicated architecture

Cited by 52 publications

References 18 publications

Architectural patterns for collaborative applications

Architectural patterns for collaborative applications

A flexible object merging framework

Distributed applications

Contact Info

Product

Resources

About