Proceedings of the 9th Annual ACM Symposium on User Interface Software and Technology - UIST '96 1996
DOI: 10.1145/237091.237093
|View full text |Cite
|
Sign up to set email alerts
|

A mechanism for supporting client migration in a shared window system

Abstract: Migrating collaborative applications to or near the workstations of active users can offer better performance in many scenarios. We have developed {3 client migration mechanism for centralized shared window systems that does not require changes to existing application and system software. It is based on logging input at the old site and replaying it at the new site. This approach raises several difficult questions: How should the log size be kept low? How should response time be kept low white migration is in … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
17
0

Year Published

1999
1999
2015
2015

Publication Types

Select...
3
2
2

Relationship

1
6

Authors

Journals

citations
Cited by 21 publications
(17 citation statements)
references
References 14 publications
(6 reference statements)
0
17
0
Order By: Relevance
“…Figure 10 shows the relationship between the logger and loggable. The logger is an extension of the distributor of [5] and thus is independent of the client collaboration system because it defines a generic format for the I/O messages. Like the client-specific translator of [5], the loggable is expected to translate between these messages and the actual I/O messages communicated between the program and user-interface components, as shown in Figure 10.…”
Section: Dynamic Replicationmentioning
confidence: 99%
See 3 more Smart Citations
“…Figure 10 shows the relationship between the logger and loggable. The logger is an extension of the distributor of [5] and thus is independent of the client collaboration system because it defines a generic format for the I/O messages. Like the client-specific translator of [5], the loggable is expected to translate between these messages and the actual I/O messages communicated between the program and user-interface components, as shown in Figure 10.…”
Section: Dynamic Replicationmentioning
confidence: 99%
“…Concurrent play/replay [5] ensures that collaboration is not paused when this log is replayed to a new replica. This technique ensures that the old replica continues to play live messages until the new replica has replayed all of the recorded messages, with the replay and play occurring concurrently.…”
Section: Other Issuesmentioning
confidence: 99%
See 2 more Smart Citations
“…Besides static workgroup topology, some research also considers dynamic changes to the workgroup and client migration [5,11], in particular accommodation of late-comers that need to be updated on the current state of the session. Two competing solutions are replaying all previous events to the newcomer vs. transmitting a current image of application state.…”
Section: Related Workmentioning
confidence: 99%