Gone but not forgotten: designing for disconnection in synchronous groupware

Simple item page
dc.contributor.authorGutwin, Carl
dc.contributor.authorGraham, T.C. Nicholas
dc.contributor.authorWolfe, Chris
dc.contributor.authorWong, Nelson
dc.contributor.authorde Alwis, Brian
dc.date.accessioned2015-07-31T21:19:44Z
dc.date.available2015-07-31T21:19:44Z
dc.date.issued2010
dc.description.abstractSynchronous groupware depends on the assumption that people are fully connected to the others in the group, but there are many situations (network delay, network outage, or explicit departure) where users are disconnected for various periods. There is little research dealing with disconnection in synchronous groupware from a user and application perspective; as a result, most current groupware systems do not handle disconnection events well, and several user-level problems occur. To address this limitation, we developed the Disco framework, a model for handling several types of disconnection in synchronous groupware. The framework considers how disconnections are identified, what senders and receivers should do during an absence, and what should be done with accumulated data upon reconnection. We have implemented the framework in three applications that show the feasibility, generality, and functionality of our ideas. Our framework is the first to deal with a full range of disconnection issues for synchronous groupware, and shows how groupware can better support the realities of distributed collaboration.en_US
dc.description.refereedYesen_US
dc.identifier.doi10.1145/1718918.1718951
dc.identifier.urihttp://hdl.handle.net/1880/50812
dc.publisherACMen_US
dc.publisher.urlhttp://dx.doi.org/10.1145/1718918.1718951en_US
dc.titleGone but not forgotten: designing for disconnection in synchronous groupwareen_US
dc.typeunknown
Files
License bundle
Now showing 1 - 1 of 1
Thumbnail Image
Name:
license.txt
Size:
1.84 KB
Format:
Item-specific license agreed upon to submission
Description:
Download
Collections
Surfnet