High-latency, low-bandwidth windowing in the Jupiter collaboration system

Nichols, David A.; Curtis, Pavel; Dixon, Michael; Lamping, John

doi:10.1145/215585.215706

Cited by 122 publications

(108 citation statements)

References 12 publications

Supporting

Mentioning

107

Contrasting

Unclassified

Order By: Relevance

“…XWiki is a java-based wiki that runs on any servlet container such as Tomcat 6 CLAUDIA-LAVINIA IGNAT, LUC ANDRÉ AND GÉRALD OSTER or Jetty. The Jupiter algorithm proposed by Nichols et al [12] required that the same algorithm is running on the server side and on the client side. Server side code is developed in Java while client side is based on standard web technology such as HTML and Javascript.…”

Section: Working Modesmentioning

confidence: 99%

See 1 more Smart Citation

Enhancing rich content wikis with real‐time collaboration

Ignat

André

Oster

2017

Concurrency and Computation

View full text Add to dashboard Cite

SUMMARYWikis are one of the most important tools of Web 2.0 allowing users to easily edit shared data. However, wikis offer limited support for merging concurrent contributions on the same pages. Users have to manually merge concurrent changes and there is no support for an automatic merging. Real-time collaborative editing reduces conflicts as the time frame for concurrent work is very short. In this paper, we propose extending wiki systems with real-time collaboration. We propose an automatic merging solution adapted for rich content wikis. Our solution relies on an operational transformation algorithm defined for high level operations that capture user actions such as move, merge and split. Copyright c 0000 John Wiley & Sons, Ltd.KEY WORDS: CSCW; collaborative editing; operational transformation; wiki INTRODUCTIONThe Web 2.0 era is associated with the growing success of participatory collaborative tools for public users. Enterprises have integrated a part of these tools in their information systems to improve their productivity and to facilitate the emergence of a form of collective intelligence.Among these tools, wikis efficiently share and structure a large amount of knowledge. Wikis are interlinked pages of rich text. Any user can view and edit these pages. For instance, a software development team can dedicate a wiki page to the minutes of their meetings, another one to their bug reports and a last one to the progress of their development. This way, everybody can keep an eye on when is the next meeting, who will attend, the minutes of a previous meeting, what are the bugs found or fixed, and the completed work on the project. Moreover, a wiki allows fast updates and everybody can edit the content without any restriction. A wiki offers all these features in a single tool.However, most existing wiki systems such as MediaWiki do not automatically merge parallel modifications on the same page. This becomes critical when changes have to be performed very quickly. A typical example is breaking news, when it is common that hundreds of people contribute to the same related Wikipedia pages in a very short amount of time. If two users are concurrently editing the same article, when they try to save their changes, the changes of only one user are published. The other user will be presented with two versions of the wiki page: the one that the user tried to publish and the recently published version. Conflicts, i.e. concurrent changes on the same article, have to be manually resolved by users by retyping or copying and pasting the changes they performed in the last version that was published. Moreover, users are unaware of other concurrent updates on the same article until they try to publish their own changes. Resolving conflicts might become very tedious, and this can be critical when a change has to be published almost instantly. * Correspondence to: Inria Centre Nancy -Grand Est, 615 rue du Jardin Botanique, 54600 Villers-lès-Nancy, FR. Email: claudia.ignat@inria. Ignat et al. [1,2,3,4] highlight the fact that co...

show abstract

Section: Working Modesmentioning

confidence: 99%

“…Any integration algorithm such as Jupiter proposed by Nichols et al [12] or SOCT4 proposed by Vidot et al [13] can be used. In our implementation we used Jupiter algorithm.…”

Section: Traditional Merging Algorithmmentioning

confidence: 99%

Enhancing rich content wikis with real‐time collaboration

Ignat

André

Oster

2017

Concurrency and Computation

View full text Add to dashboard Cite

show abstract

“…Note that the term ACE is simply the name for the editor instead of an acronym. The editor is written in Java and it implements the Jupiter algorithm [12]. The Jupiter algorithm is a centralized algorithm for participant coordination and operational transformation.…”

Section: The Ace Collaborative Editormentioning

confidence: 99%

Towards Trustworthy Collaborative Editing

Babi¹,

Zhao²

2017

Computers

View full text Add to dashboard Cite

Real-time collaborative editing applications are drastically different from typical client-server applications in that every participant has a copy of the shared document. In this type of environment, each participant acts as both a client and a server replica. In this article, we elaborate on how to adapt Byzantine fault tolerance (BFT) mechanisms to enhance the trustworthiness of such applications. It is apparent that traditional BFT algorithms cannot be used directly because it would dictate that all updates submitted by participants be applied sequentially, which would defeat the purpose of collaborative editing. The goal of this study is to design and implement an efficient BFT solution by exploiting the application semantics and by doing a threat analysis of these types of applications. Our solution can be considered as a form of optimistic BFT in that local states maintained by each participant may diverge temporarily. The states of the participants are made consistent with each other by a periodic synchronization mechanism.

show abstract

“…Other groupware systems, such as Groupkit [14] and Jupiter [11], also provide an infrastructure for conference management and application sharing. However, they lack system-level support for dynamic shared object specification, group state transfer, and persistent groups, the last of which is made possible by Corona's message logging.…”

Section: Related Workmentioning

confidence: 99%