ContentEngine - Revision history

202.38.48.191: /* OfflineEditing */

2007-05-06T11:05:27Z

‎OfflineEditing

202.38.48.191 at 11:02, 6 May 2007

2007-05-06T11:02:34Z

202.38.48.191: /* [OfflineEditing] */

2007-05-06T10:49:47Z

‎[OfflineEditing]

202.38.48.191: /* Offline Editing [OfflineEditing] */

2007-05-06T10:49:27Z

‎Offline Editing [OfflineEditing]

202.38.48.191: /* Offline Editing */

2007-05-06T10:49:02Z

‎Offline Editing

202.38.48.191 at 10:46, 6 May 2007

2007-05-06T10:46:38Z

Arif Iqbal at 08:23, 6 May 2007

2007-05-06T08:23:12Z

Arif Iqbal at 08:20, 6 May 2007

2007-05-06T08:20:41Z

Arif Iqbal at 07:53, 6 May 2007

2007-05-06T07:53:54Z

Arif Iqbal at 07:28, 6 May 2007

2007-05-06T07:28:28Z

@@ Line 36: / Line 36: @@
 = [[OfflineEditing]] =
-Users can edit documents in the offline mode. Just to make sure that they users have the latest copy of the chunk, the Content Engine send the hash along with the document. So, when user tries to synchronize with the server, system knows whether he had the latest copy or the old one. If the user has the latest copy, the Content Engine just updates the page and point the name to the latest chunk.
+Users can edit documents in the offline mode. Just to make sure that they users have the latest copy of the chunk, the Content Engine send the hash along with the document. So, when user tries to synchronize with the server, system knows whether he had the latest copy of the chunk or the old one. If the user has the latest copy, the Content Engine just updates the page and point the name to the latest chunk.
 In case, the user don't have the latest copy when they try to synchronize then they are given an option to merge the document with the latest copy or to overwrite the latest copy. The Content Engine will highlight the changes in the latest version and the users version.

← Older revision		Revision as of 11:02, 6 May 2007
Line 36:		Line 36:
	= [[OfflineEditing]] =		= [[OfflineEditing]] =

−	~~User~~	+	Users can edit documents in the offline mode. Just to make sure that they users have the latest copy of the chunk, the Content Engine send the hash along with the document. So, when user tries to synchronize with the server, system knows whether he had the latest copy or the old one. If the user has the latest copy, the Content Engine just updates the page and point the name to the latest chunk.
		+
		+	In case, the user don't have the latest copy when they try to synchronize then they are given an option to merge the document with the latest copy or to overwrite the latest copy. The Content Engine will highlight the changes in the latest version and the users version.

@@ Line 34: / Line 34: @@
 * The two different chunks with different names might intersect(i.e. their contents are same) at some point in time. The chunks might merge at this stage and follow the same path onwards or they may take the different paths altogether. At this stage, the users may decide to merge the two names together that is only one chunk with two names pointing to it OR they may want to follow different paths with names pointing to different chunks.
-= [OfflineEditing] =
+= [[OfflineEditing]] =
 User

@@ Line 34: / Line 34: @@
 * The two different chunks with different names might intersect(i.e. their contents are same) at some point in time. The chunks might merge at this stage and follow the same path onwards or they may take the different paths altogether. At this stage, the users may decide to merge the two names together that is only one chunk with two names pointing to it OR they may want to follow different paths with names pointing to different chunks.
-= Offline Editing [OfflineEditing] =
+= [OfflineEditing] =
 User

← Older revision		Revision as of 10:49, 6 May 2007
Line 34:		Line 34:
	* The two different chunks with different names might intersect(i.e. their contents are same) at some point in time. The chunks might merge at this stage and follow the same path onwards or they may take the different paths altogether. At this stage, the users may decide to merge the two names together that is only one chunk with two names pointing to it OR they may want to follow different paths with names pointing to different chunks.		* The two different chunks with different names might intersect(i.e. their contents are same) at some point in time. The chunks might merge at this stage and follow the same path onwards or they may take the different paths altogether. At this stage, the users may decide to merge the two names together that is only one chunk with two names pointing to it OR they may want to follow different paths with names pointing to different chunks.

−	= Offline Editing =	+	= Offline Editing [OfflineEditing] =
		+
		+	User

@@ Line 6: / Line 6: @@
 * Intially, Content Engine wont have any name "ABC" that live in the system.
-* By creating the document "ABC", the system will add a name "ABC" in the engine and will point this to a vertex i.e. first version of this document.
+* By creating the document "ABC", the system will add a name "ABC" in the engine and will point this to a vertex(chunk) i.e. first version of this document.
 ABC ---> ( doc1 )
 * Now Alex edits the document and saves another version. At this stage, our system will add another vertex and will now point the name "ABC" to this newer version
@@ Line 29: / Line 29: @@
                         -----> (doc5) -> (doc6) <---- ABC
                        |                   |
-(doc1) -> (doc2) -> (doc3) -> (doc4) -----^
+(doc1) -> (doc2) -> (doc3) -> (doc4) -----
-Consider the Content Engine as a graph where
+= Offline Editing =

← Older revision		Revision as of 08:23, 6 May 2007
Line 30:		Line 30:
	\| \|		\| \|
	(doc1) -> (doc2) -> (doc3) -> (doc4) -----^		(doc1) -> (doc2) -> (doc3) -> (doc4) -----^
		+

@@ Line 2: / Line 2: @@
 Our engine borrows heavily from the concepts of the [http://git.or.cz/ Git - Fast Version Control System].
 To understand how Content Engine works, lets take an example in which Alex and Bob edit documents in the content engine. Lets say Alex creates a document named "ABC" in the content engine. Lets take the steps through which the Content Engine will go through
-* Intially, content engine wont have any name "ABC" and any such document in the system.
+* Intially, Content Engine wont have any name "ABC" that live in the system.
-* By creating the document "ABC", the system will add a name "ABC" in our engine and will point this to a vertex i.e. first version of this document.
+* By creating the document "ABC", the system will add a name "ABC" in the engine and will point this to a vertex i.e. first version of this document.
 ABC ---> ( doc1 )
-* Now Alex edits the document and saves another version. At this stage, our system will add another vertex and will point the name "ABC" to this new version
+* Now Alex edits the document and saves another version. At this stage, our system will add another vertex and will now point the name "ABC" to this newer version
 (doc1) -> (doc2)
+             ^
+             |
             ABC
-So, now ABC points to doc2 i.e. the new version of the document.
+So, now ABC now points to doc2 i.e. the new version of the document.
 * Now, another user Bob comes and they both start editing the document pointed to by name "ABC" and Bob creates a new version
 (doc1) -> (doc2) -> (doc3)
@@ Line 31: / Line 20: @@
                       ABC
 * Alice and Bob now decides that they have different views on topic "ABC" and they rather have their own versions of this topic. So, they the content engine looks like
-(doc1) -> (doc2) -> (doc3) -> (doc4) -> (doc5) <--- ABC
+so, Alice has her thoughts in doc4 and Bob in doc5.
+* Later on, their ideas again intersect and now they would like to have their pages combined again on the topic ABC.
+So, Content Engine now takes the sophisticated union of these documents and merge them in a single document i.e. doc6.
-                               ABC
+                       -----> (doc5) -> (doc6) <---- ABC
-so, Alice has a version of doc4 and Bob has doc5.
+                      |                   |
+Vertex = Particular version of a document
+Edge = Connecting different versions of documents
-* We have a big content dictionary and it is stored in normal files on a file system.
+Name = Name points to a vertex i.e. document

← Older revision		Revision as of 07:53, 6 May 2007
Line 9:		Line 9:
	Name = Name points to a vertex i.e. document		Name = Name points to a vertex i.e. document

		+
		+	Lets consider someone who creates a document with a name "Alex". Alex name points to a particular version of
	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.		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.


		+	To understand how Content Engine works, lets take an example in which Alex and Bob edit documents in the content engine. Lets say Alex creates a document named "ABC" in the content engine. Lets take the steps through which the Content Engine will go through
		+
		+	* Intially, content engine wont have any name "ABC" and any such document in the system.
		+	* By creating the document "ABC", the system will add a name "ABC" in our engine and will point this to a vertex i.e. first version of this document.
		+	ABC ---> ( doc1 )
		+	* Now Alex edits the document and saves another version. At this stage, our system will add another vertex and will point the name "ABC" to this new version
		+	(doc1) -> (doc2)
		+	^
		+	\|
		+	ABC
		+	So, now ABC points to doc2 i.e. the new version of the document.
		+	* Now, another user Bob comes and they both start editing the document pointed to by name "ABC" and Bob creates a new version
		+	(doc1) -> (doc2) -> (doc3)
		+	^
		+	\|
		+	ABC
		+	* Alice and Bob now decides that they have different views on topic "ABC" and they rather have their own versions of this topic. So, they the content engine looks like
		+
		+	(doc1) -> (doc2) -> (doc3) -> (doc4) -> (doc5) <--- ABC
		+	^
		+	\|
		+	ABC
		+	so, Alice has a version of doc4 and Bob has doc5.

@@ Line 1: / Line 1: @@
 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.
+*
 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.