Resource sharing for replicated synchronous groupware

Abstract

Abstract-We describe problems associated with accessing data resources external to the application, which we term externalities, in replicated synchronous collaborative applications. Accessing externalities such as files, databases, network connections, environment variables, and the system clock is not as straightforward in replicated collaborative software as in single-user applications or centralized collaborative systems. We describe ad hoc solutions that add to development cost and complexity because the developer must program different behavior for different replicas.We introduce a novel general approach to accessing externalities uniformly in a replicated collaborative system. The approach uses a semireplicated architecture where the actual externality resides at a single location and is accessed via replicated proxies. This approach allows developers of replicated synchronous groupware to 1) use similar externality access mechanisms as in traditional single-user applications, and 2) program all replicas to execute the same behavior. We describe a general design for proxied access to read-only, write-only, and read-write externalities and discuss the tradeoffs of this semireplicated approach over full, literal replication and the class of applications to which this approach can be successfully applied. We also describe details of a prototype implementation of this approach within a replicated collaboration-transparency system, called Flexible JAMM (Java Applets Made Multiuser).

Temporality in Medical Work: Time also Matters

“…An extensive collection of research investigations surrounds such topics as distributed teams (Olson and Teasley, 1996;Grinter et al, 1999;Mark et al, 2003), computer-mediated communication (Galegher and Kraut, 1990;Markus, 1994;Bos et al, 2002), and more recent phenomena such as distributed gaming (Ducheneaut and Moore, 2004). A wide range of tools, such as multimedia communication systems (Gaver et al, 1992;Bly et al, 1993), collaborative workspaces (Bently et al, 1997) and tools for synchronous collaboration (Begole et al, 2001;Sun and Chen, 2002), have attempted to overcome the problems of distribution by simulating aspects of co-presence. For instance, facilities for distributed work are now incorporated into personal computer operating systems as a matter of course.…”

Making AutoCAD Collaborative: Implementation and Application of CoAutoCAD

“…Another approach is to develop generic application sharing environment and add the functions of singeruser applications to the environment [5]. It can make collaborative software having powerful functions.…”

Research and Implementation of Groupware in Chemical Collaborative Research Environment

“…We made use of centralized architecture in the construction of the CARE-G net architecture, because the key advantage of centralized architectures is that they have no problem with data consistency because there is only one copy [18],Fig1.So this architecture can easy control concurrent [19]. But purely centralized systems impose strict What You See Is What I See (WYSIWIS), where the participants see exactly the same view of the shared application at the same time [20], which disallows independent work.…”