
TL;DR
This paper explores storing wiki pages in a tuple space to improve consistency and efficiency, analyzing how this approach impacts the user experience and addressing issues like deadlocks and edit contention.
Contribution
It introduces a novel tuple space-based architecture for wikis, demonstrating how this method can mitigate common concurrency problems and alter the traditional wiki experience.
Findings
Tuple space storage reduces deadlocks and edit conflicts.
Retrieval by templates simplifies page access and editing.
The approach offers a new paradigm for collaborative editing systems.
Abstract
We consider storing the pages of a wiki in a tuple space and the effects this might have on the wiki experience. In particular, wiki pages are stored in tuples with a few identifying values such as title, author, revision date, content, etc. and pages are retrieved by sending the tuple space templates, such as one that gives the title but nothing else, leaving the tuple space to resolve to a single tuple. We use a tuple space wiki to avoid deadlocks, infinite loops, and wasted efforts when page edit contention arises and examine how a tuple space wiki changes the wiki experience.
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsWikis in Education and Collaboration · Natural Language Processing Techniques · Software Engineering Research
