Difference between revisions of "ContentEngine"
Arif Iqbal (talk | contribs) |
Arif Iqbal (talk | contribs) |
||
| Line 1: | Line 1: | ||
The [[ContentEngine]] is the foundation on which [[TopSoil]] is built. | The [[ContentEngine]] is the foundation on which [[TopSoil]] is built. | ||
| − | Our engine borrows heavily from the concepts of the [http://git.or.cz/ Git - Fast Version Control System] | + | Our engine borrows heavily from the concepts of the [http://git.or.cz/ Git - Fast Version Control System]. |
| − | * Content Engine ensures to properly synchronizes the changes made by people using [[OfflineEditing]] i.e. the offline mode. | + | |
| + | Consider the Content Engine as a graph where | ||
| + | |||
| + | Vertex = Particular version of a document | ||
| + | Edge = Connecting different versions of documents | ||
| + | Name = Name points to a vertex i.e. document | ||
| + | |||
| + | If a single name points to multiple vertices(documents) then we have ambiguity for choosing a document based on its name e.g "cricket" name can actually point to the bug cricket and game cricket. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | * We have a big content dictionary and it is stored in normal files on a file system. | ||
| + | * Content Engine ensures to properly synchronizes the changes made by people using [[OfflineEditing]] i.e. the offline mode. | ||
* | * | ||
The way we think to solve this problem is by letting our content engine to take the union of the content changes that the editors have made. | The way we think to solve this problem is by letting our content engine to take the union of the content changes that the editors have made. | ||
Revision as of 07:28, 6 May 2007
The ContentEngine is the foundation on which TopSoil is built.
Our engine borrows heavily from the concepts of the Git - Fast Version Control System.
Consider the Content Engine as a graph where
Vertex = Particular version of a document Edge = Connecting different versions of documents Name = Name points to a vertex i.e. document
If a single name points to multiple vertices(documents) then we have ambiguity for choosing a document based on its name e.g "cricket" name can actually point to the bug cricket and game cricket.
- We have a big content dictionary and it is stored in normal files on a file system.
- Content Engine ensures to properly synchronizes the changes made by people using OfflineEditing i.e. the offline mode.
The way we think to solve this problem is by letting our content engine to take the union of the content changes that the editors have made.
