Difference between revisions of "Extension talk:P2P.php"
(concept) |
|||
| Line 1: | Line 1: | ||
== Concept == | == Concept == | ||
| − | To develop the [[PeerPedia]] solution using a standard MediaWiki code base running on every peer. The peer-based MediaWiki doesn't need to be highly scalable and so doesn't require a powerful database server like MySQL or PostgreSQL and doesn't require a standalone web-server like Apache either. [[Extension: | + | To develop the [[PeerPedia]] solution using a standard MediaWiki code base running on every peer. The peer-based MediaWiki doesn't need to be highly scalable and so doesn't require a powerful database server like MySQL or PostgreSQL and doesn't require a standalone web-server like Apache either. [[Extension talk:MediaWikiLite.php|MediaWikiLite extension]] is being developed to replace the database server with the [http://www.sqlite.org SQLite] PHP library and to allow the MediaWiki PHP code to run as a daemon which communicates directly with its clients over an HTTP socket instead of running as a module or CGI of a web server. |
| − | This extension is used in conjunction with [[Extension: | + | === DHT === |
| + | This extension is used in conjunction with the [[Extension talk:MediaWikiLite.php|MediaWikiLite extension]] to allow a P2P layer directly connect clients who are editing the same articles so that they can synchronise data, reduce edit-conflicts and act as redundant caches for the data they share. Eventually the P2P layer should incorporate a [[DHT]] to maintain indexes of active peers and the article content they hold. | ||
| + | |||
| + | === Synchronisation === | ||
| + | The P2P layer also allows users to work offline and have their changes synchronise when internet bandwidth becomes available. In these cases, edit conflicts would need to be handled using the workflow system since there could be many revisions by the time synchronisation occurs. | ||
== See also == | == See also == | ||
Revision as of 01:00, 7 January 2008
Contents
Concept
To develop the PeerPedia solution using a standard MediaWiki code base running on every peer. The peer-based MediaWiki doesn't need to be highly scalable and so doesn't require a powerful database server like MySQL or PostgreSQL and doesn't require a standalone web-server like Apache either. MediaWikiLite extension is being developed to replace the database server with the SQLite PHP library and to allow the MediaWiki PHP code to run as a daemon which communicates directly with its clients over an HTTP socket instead of running as a module or CGI of a web server.
DHT
This extension is used in conjunction with the MediaWikiLite extension to allow a P2P layer directly connect clients who are editing the same articles so that they can synchronise data, reduce edit-conflicts and act as redundant caches for the data they share. Eventually the P2P layer should incorporate a DHT to maintain indexes of active peers and the article content they hold.
Synchronisation
The P2P layer also allows users to work offline and have their changes synchronise when internet bandwidth becomes available. In these cases, edit conflicts would need to be handled using the workflow system since there could be many revisions by the time synchronisation occurs.
