SimultaneousEditing - Revision history

202.38.48.191: /* A simple editing scenario */

2007-05-06T10:31:50Z

‎A simple editing scenario

202.38.48.191: /* A simple editing scenario */

2007-05-06T10:09:08Z

‎A simple editing scenario

Athar Hameed at 08:40, 6 May 2007

2007-05-06T08:40:21Z

Athar Hameed at 07:52, 6 May 2007

2007-05-06T07:52:47Z

Athar Hameed at 07:52, 6 May 2007

2007-05-06T07:52:25Z

Athar Hameed at 07:30, 6 May 2007

2007-05-06T07:30:08Z

New page

Simultaneous editing is part of [[Topsoil]].

We want people to be able to edit a web page simultaneously. Two major problems with simultaneous editing are conflict resolution and content divergence. What we want is that users should be able to see other users editing the same document in real time. This can be accomplished using an architecture where clients poll the server for changes and incorporate those changes in the current document as they come in. Imagine two users editing a single document. The first user could be editing the first paragraph and the second user could be making changes to the second paragraph. Each user will see the other user's changes as they are being made. If both users happen to edit the same thing, a conflict resolution facility could be provided, using which the users could either come up with a collaborative edit or all users could back off allowing only one user to make the change.

@@ Line 22: / Line 22: @@
-what sort of overhead is associated with sending the edits to servers?
+*what is an edit
-what involves sending an edit to the server?
+an edit involves, an addition, modification, or deletion in a document.
-how are batches made and why?
+* what sort of overhead is associated with sending the edits to servers?
-how does a time-out operate?
+we don't want to incur any overhead when sending edits to the server. do avoid overheads, we will bunch together several edits and send them to the server in a batch. of course, with less frequent edits, we will send the edits to the server any way after a some time-out period. the number of edits to be bundled together should be such that there is a balance between edit update latency and the size of edit batch.
-how does the server make edits available to other users?
+* what involves sending an edit to the server?
-what edits are sent to the client? all edits since the last time a particular client requested edits, or the current edits on the server only? note that if only the current edits are sent, a client could potentially miss out on edits if it gets disconnected in between.
+we will have to come up with a scheme for sending edits to the server. what exactly do we report?
-look up comet?
+* how are batches made and why?

← Older revision		Revision as of 10:09, 6 May 2007
Line 20:		Line 20:

	Primary concerns in this architecture are those of excessive requests hitting the server simultaneously and the response times involved. Slow response times can have a possibly have a bad effect on the user experience.		Primary concerns in this architecture are those of excessive requests hitting the server simultaneously and the response times involved. Slow response times can have a possibly have a bad effect on the user experience.
		+
		+
		+	what sort of overhead is associated with sending the edits to servers?
		+	what involves sending an edit to the server?
		+	how are batches made and why?
		+	how does a time-out operate?
		+	how does the server make edits available to other users?
		+	what edits are sent to the client? all edits since the last time a particular client requested edits, or the current edits on the server only? note that if only the current edits are sent, a client could potentially miss out on edits if it gets disconnected in between.
		+	look up comet?

← Older revision		Revision as of 08:40, 6 May 2007
Line 17:		Line 17:

	4. User B and C receive the edit which gets incorporated in their editing panes.		4. User B and C receive the edit which gets incorporated in their editing panes.
		+
		+
		+	Primary concerns in this architecture are those of excessive requests hitting the server simultaneously and the response times involved. Slow response times can have a possibly have a bad effect on the user experience.

← Older revision		Revision as of 07:52, 6 May 2007
Line 4:		Line 4:


−	* A simple editing scenario	+	= A simple editing scenario =

	User A, B and C are editing the document, "The quick brown fox jumps over the lazy dog".		User A, B and C are editing the document, "The quick brown fox jumps over the lazy dog".

← Older revision		Revision as of 07:52, 6 May 2007
Line 2:		Line 2:

	We want people to be able to edit a web page simultaneously. Two major problems with simultaneous editing are conflict resolution and content divergence. What we want is that users should be able to see other users editing the same document in real time. This can be accomplished using an architecture where clients poll the server for changes and incorporate those changes in the current document as they come in. Imagine two users editing a single document. The first user could be editing the first paragraph and the second user could be making changes to the second paragraph. Each user will see the other user's changes as they are being made. If both users happen to edit the same thing, a conflict resolution facility could be provided, using which the users could either come up with a collaborative edit or all users could back off allowing only one user to make the change.		We want people to be able to edit a web page simultaneously. Two major problems with simultaneous editing are conflict resolution and content divergence. What we want is that users should be able to see other users editing the same document in real time. This can be accomplished using an architecture where clients poll the server for changes and incorporate those changes in the current document as they come in. Imagine two users editing a single document. The first user could be editing the first paragraph and the second user could be making changes to the second paragraph. Each user will see the other user's changes as they are being made. If both users happen to edit the same thing, a conflict resolution facility could be provided, using which the users could either come up with a collaborative edit or all users could back off allowing only one user to make the change.
		+
		+
		+	* A simple editing scenario
		+
		+	User A, B and C are editing the document, "The quick brown fox jumps over the lazy dog".
		+
		+	1. User A makes an edit by changing 'quick' to 'QUICK'.
		+
		+	Edits are sent to the server in batches. A time-out makes sure that the edits are sent to the server even if a complete batch is not ready. A similar mechanism is used on the server side. Clients receive edits in batches or when there is a time-out on the server.
		+
		+	2. User A sends the edit to the server.
		+
		+	3. Server makes the edit available to other users.
		+
		+	4. User B and C receive the edit which gets incorporated in their editing panes.