Concurrency awareness in a P2P wiki system

Alshattnawi, Sawsan; Canals, Gérôme; Molli, Pascal

doi:10.1109/cts.2008.4543942

Cited by 7 publications

(10 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…These systems propose improved algorithms to merge conflicting concurrent updates. As such, these systems provide interesting features such as concurrency awareness, which allows users to know whether a page is the result of an automatic merge by the system or not, and highlights the parts of a page that are subject to concurrency mismatches [5]. However, these systems use a similar architecture as XWiki Concerto, so they would exhibit similar strengths and weaknesses as XWiki Concerto for hosting a Wikipedia-like workload.…”

Section: Xwiki Concertomentioning

confidence: 99%

Wikipedia workload analysis for decentralized hosting

2009

View full text Add to dashboard Cite

a b s t r a c tWe study an access trace containing a sample of Wikipedia's traffic over a 107-day period aiming to identify appropriate replication and distribution strategies in a fully decentralized hosting environment. We perform a global analysis of the whole trace, and a detailed analysis of the requests directed to the English edition of Wikipedia. In our study, we classify client requests and examine aspects such as the number of read and save operations, significant load variations and requests for nonexisting pages. We also review proposed decentralized wiki architectures and discuss how they would handle Wikipedia's workload. We conclude that decentralized architectures must focus on applying techniques to efficiently handle read operations while maintaining consistency and dealing with typical issues on decentralized systems such as churn, unbalanced loads and malicious participating nodes.

show abstract

Section: Xwiki Concertomentioning

confidence: 99%

Wikipedia workload analysis for decentralized hosting

2009

View full text Add to dashboard Cite

show abstract

“…For instance, the linux kernel is developed by thousands of programmers around the world using Git [39]. Several web-based hosting services for software development projects provide large DVCS history such as GitHub (3.4M developers and 6.5M repositories) 2 , Assembla (800,000 developers and more than 100,000 projects) 3 , or SourceForge(3.4M developers and 324,000 projects) 4 . In this paper, we selected traces from the most used system: Git.…”

Section: A Corpus Availablementioning

confidence: 99%

“…An awarness mechanism can be independently added upon the same kind of merge algorithm without affecting their result [12], [3]. So, an awarness mechanism can be added in system upon CMUndo algorithm.…”

Section: Related Workmentioning

confidence: 99%

Improving Textual Merge Result

Ahmed-Nacer¹,

Urso²,

Charoy³

2013

Proceedings of the 9th IEEE International Conference on Collaborative Computing: Networking, Applications and Worksharing

View full text Add to dashboard Cite

Abstract-In asynchronous collaborative systems, merging is an essential component. It allows to reconcile modifications made concurrently as well as managing software change through branching. The collaborative system is in charge to propose a merge result that includes user's modifications. The users now have to check and adapt this result. The adaptation should be as effort-less as possible, otherwise, the users may get frustrated and will quit the collaboration.The objective of this paper is to improve the result quality of the textual merge tool that constitutes the default merge tool of distributed version control systems. The basic idea is to study the behavior of the concurrent modifications during merge procedure. We identified when the existing merge techniques under-perform, and we propose solutions to improve the quality of the merge. We finally compare with the traditional merge tool through a large corpus of collaborative editing.

show abstract

“…Unfortunately, they don't take into account the concurrency. The work presented in this paper is based on the concurrency awareness mechanism and the results obtained from our work presented in [4]. The objective of the concurrency awareness mechanism is to recognize the server produced pages and the user produced pages and if the page is server produced to highlight the effects of concurrent updates inside these pages.…”

Section: Revision Histories In Collaborative Editorsmentioning

confidence: 99%

“…In this case the page is server-produced. While when the merge is done under the control of the user the page is user-produced [4]. Our objective in this paper is to represent the history of P2P wiki pages by adding information about the pages state if it either user-produced or server-produced.…”

Section: Introductionmentioning

confidence: 99%

A Nonlinear Representation of Page History in P2P Wiki System

Alshattnawi¹,

Canals²,

Molli³

Towards Sustainable Society on Ubiquitous Networks

Self Cite

View full text Add to dashboard Cite

Awareness about the document evolution is an important part in collaborative editing systems. It is represented always by the versions history. The representation of the document history in centralized collaborative editing systems is linear. However, in distributed collaborative editors, there is no central server and the users can work asynchronously or in isolation and some versions may be produced concurrently, in this case, the history is no long linear. The existing history representations are limited because they don't provide any information about the concurrence on the document history. We introduce here a non linear representation for the page history in P2P wiki systems. The concurrency information about the page versions is provided; the user can explore the page versions that resulted under the user's control or produced by the server in case of merging concurrent modifications.

show abstract

Concurrency awareness in a P2P wiki system

Cited by 7 publications

References 16 publications

Wikipedia workload analysis for decentralized hosting

Wikipedia workload analysis for decentralized hosting

Improving Textual Merge Result

A Nonlinear Representation of Page History in P2P Wiki System

Contact Info

Product

Resources

About