chiark / gitweb /
wip new, tidying
authorIan Jackson <ijackson@chiark.greenend.org.uk>
Sun, 28 Jun 2020 15:18:04 +0000 (16:18 +0100)
committerIan Jackson <ijackson@chiark.greenend.org.uk>
Sun, 28 Jun 2020 15:18:04 +0000 (16:18 +0100)
PROTOCOL.md [moved from NOTES with 88% similarity]

similarity index 88%
rename from NOTES
rename to PROTOCOL.md
index 75340394c4467967069e65325508fe577dc0f316..35ea9b251edf2154dabd5f90e3157fb52c89555e 100644 (file)
--- a/NOTES
@@ -1,71 +1,5 @@
-PROTOCOL
-
-
-all in context of a piece
-
-
- client                                server
-
-        <-------------------
-       some update
-               piece
-               gen
-               your doing ?
-
-at start of op
- note picee.gen = gen
-
- grab, or move, or something:
-       ------------------->
-       grab/move/ungrab
-               piece
-               piece.gen
-                                       if piece.gen == msg.piece.gen
-                                       then set piece.last_client
-
-                                       if piece.last_client == client
-                                       then ok
-
-                                       otherwise bad
-                                       send nothing!  a message
-                                       must be in the queue already!
-
-        <-------------------
-       soem update
-               piece
-               gen
-               your doing ?
-
-if "your doing"
-ignore the message, we are up to date,
-but set the piece's gen
-
-otherwise
-cancel any drag for the piece
-reset the piece state to that specified
-
-
---------------------------------------------------
-
-client maintains
-       for each piece
-               [ game state ]
-               gen (last from server)
-               x, y, held
-       overall
-               [ ui state ]
-               what are we dragging, drag start, click state, etc.
-
-server maintains
-       for each piece
-               gen
-       client list etc.
-
---------------------------------------------------
-
-
-ANALYSIS
-========
+CONCURRENT UPDATE PROTOCOL AND ANALYSIS
+=======================================
 
 (Assumption: our network techniques deliver messages in order in both
 directions between a server and a client; failure of the communication