A mechanism for supporting client migration in a shared window system

Chung, Goopeel; Dewan, Prasun

doi:10.1145/237091.237093

Cited by 21 publications

(17 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

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%

“…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%

“…In the centralized case, however, the location of the central program replica does not normally change -most systems only allow new user-interface components to be added. An exception is the XTV shared X system, which allows dynamic migration of the centralized X program [5]. The Presence-AR spreadsheet of the Advanced Reality Corporation promises dynamic transition from the replicated to the centralized architecture as the number of users increases beyond some threshold.…”

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%

See 3 more Smart Citations

Towards dynamic collaboration architectures

Chung

Dewan

2004

Proceedings of the 2004 ACM Conference on Computer Supported Cooperative Work

Self Cite

View full text Add to dashboard Cite

In this paper, we introduce the concept of dynamically changing between centralized, replicated, and hybrid collaboration architectures. It is implemented by providing users a function that dynamically changes the mapping between user-interface and program components. We decompose the function into more primitive commands that are executed autonomously by individual users. These commands require a mechanism to dynamically replicate user-interface and program components on a user's site. We present a logging approach for implementing the mechanism that records input (output) messages sent to one incarnation of a program (user-interface) component, and replays the recorded messages to a different incarnation of the component. Preliminary experiments with an implementation of the mechanism show that response and completion times can improve by dynamically changing the architecture to adapt to changes to the set of users in a collaboration session involving a mix of mobile and stationary devices.

show abstract

Section: Dynamic Replicationmentioning

confidence: 99%

Section: Other Issuesmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

See 2 more Smart Citations

Towards dynamic collaboration architectures

Chung

Dewan

2004

Proceedings of the 2004 ACM Conference on Computer Supported Cooperative Work

Self Cite

View full text Add to dashboard Cite

show abstract

“…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%

Distributed Applications for Collaborative Three-Dimensional Workspaces

Schmalstieg

Reitmayr

Hesina

2003

Presence: Teleoperators & Virtual Environments

View full text Add to dashboard Cite

show abstract

Middleware support for distributed multimedia and collaborative computing

Birman

Friedman

Hayden

et al. 1999

Softw: Pract. Exper.

View full text Add to dashboard Cite

Maestro is a middleware support tool for distributed multimedia and collaborative computing applications. These applications share a common need for managing multiple subgroups while providing possibly different quality-of-service guarantees for each of these groups. Maestro's functionality maps well into these requirements, and can significantly shorten the development time of such applications. In this paper, we report on Maestro, and demonstrate its utility in implementing several multimedia and collaborative computing applications. In particular, we provide a detailed description of the implementation of IMUX, a pseudo X-server (proxy) for collaborative computing applications that is based on Maestro.tools. In a video conference session, there can be a situation in which participants are connected by a WAN, but subsets of the participants may share the same LAN. Different subsets of the participants in a video conference may require different quality video streams, depending on their locale and equipment. We would probably want to use a video coding scheme similar to that used in earlier work [2][3][4]. Here, one stack is used for low quality frames, which should be delivered to all participants, while another is used for higher quality frames, and delivered only to participants running on nodes that are connected through high bandwidth links to the video sender. In addition, audio data should be delivered in FIFO order, but does not need stronger end-to-end reliability. Indeed, an attempt to overcome infrequent packet loss through a TCP-style flow control and acknowledgement mechanism might introduce undesired latency jitters and hence reduce the perceived reliability of the audio channel. On the other hand, text in the chat area should be delivered reliably and all participants should see postings in the same order.One can also imagine configurations in which subsets of participants would maintain their own private chat groups or side-band conferencing sessions. Such a feature might be useful, for example, in a business negotiation that brings together multiple representatives of one organization in the context of a larger group of participants.Application-sharing systems also demonstrate the need for multiple data streams with independent membership. For example, application multiplexors in the X Windows environment are typically implemented by interposing a 'pseudo-server' between clients and servers. The pseudo-server assumes the role of an X server when interacting with X clients and the role of an X client when interacting with an X server. When input operations are restricted to a single host, an X pseudo-server provides 'output multiplexing', allowing the output of a single application to be viewed simultaneously on multiple screens [6]. An alternate approach called 'input multiplexing' [7,8] replicates the client and employs a simplified pseudo-server. Output operations are passed to the local X server while input operations are multiplexed and communicated to remote replicas via the pseudo-server. ...

show abstract

A mechanism for supporting client migration in a shared window system

Cited by 21 publications

References 14 publications

Towards dynamic collaboration architectures

Towards dynamic collaboration architectures

Distributed Applications for Collaborative Three-Dimensional Workspaces

Middleware support for distributed multimedia and collaborative computing

Contact Info

Product

Resources

About