1993
DOI: 10.1109/2.179162
|View full text |Cite
|
Sign up to set email alerts
|

Accommodating latecomers in shared window systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
11
0

Year Published

1996
1996
2004
2004

Publication Types

Select...
6
3
1

Relationship

1
9

Authors

Journals

citations
Cited by 21 publications
(11 citation statements)
references
References 3 publications
0
11
0
Order By: Relevance
“…A variety of techniques, collectively referred to as process migration, can be used to copy an active process from one execution environment to another. Two common process migration schemes are event replay, where the system logs all state-changing events during process execution and replays them to a new instance of the process, and image-copy, where an image of the process in memory is copied [Chung and Dewan 1996] (see also Begole et al [1997b] Flexible Collaboration Transparency • and Chung et al [1993] for more details on process migration for groupware). Event replay has two disadvantages: (1) the migration time depends on the length of the execution and (2) potentially expensive operations are executed multiple times.…”
Section: Platform Requirementsmentioning
confidence: 99%
“…A variety of techniques, collectively referred to as process migration, can be used to copy an active process from one execution environment to another. Two common process migration schemes are event replay, where the system logs all state-changing events during process execution and replays them to a new instance of the process, and image-copy, where an image of the process in memory is copied [Chung and Dewan 1996] (see also Begole et al [1997b] Flexible Collaboration Transparency • and Chung et al [1993] for more details on process migration for groupware). Event replay has two disadvantages: (1) the migration time depends on the length of the execution and (2) potentially expensive operations are executed multiple times.…”
Section: Platform Requirementsmentioning
confidence: 99%
“…Two competing solutions are replaying all previous events to the newcomer vs. transmitting a current image of application state. Because the history of previous events can become arbitrarily large despite potential for compression [10], recent work favors the image copy approach [42]. This is partly due to novel architectures that make it easy to marshal complex runtime structures [3], and is also the foundation for our application migration facility.…”
Section: Related Workmentioning
confidence: 99%
“…For example, XTV uses logging for replicating both the user-interface component [8] and the program component [5]. Examples of log-based distributed systems include Coda [9] and Cygnus [10].…”
Section: Related Workmentioning
confidence: 99%