add notes

jbakse · Jan 27, 2022 · 416827d · 416827d
1 parent c30e8af
commit 416827d
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 0 deletions.
diff --git a/notes/design_questions.md b/notes/design_questions.md
@@ -17,6 +17,9 @@
 
 - should p5.party have some kind of write locking support so you can open a shared object in read only mode, or designate the writer for an object and get warnings if someone else writes?
 
+  - it would probably be common to have particpiants be read only, but me/my be writeable
+  - maybe a "host" write only mode, that warns/blocks if non host writes
+
 - should p5.party provide an id for each participant? it does have an internal id. This might be especially helpful if we support a participant leaving and coming back via a local storage "cookie".
 
 - should we support a client levaning and coming back as the same participant (e.g. a browser reload)?

diff --git a/notes/todo.todo b/notes/todo.todo
@@ -3,6 +3,14 @@
 
 ## Bugs
 
+-- Getting invalid state transition when another client leaves
+	state-machine.js:37 Invalid state transition.
+	Details: {"transition":13,"fromState":"DELETING"} 
+	History: 
+	From READY to DELETING via 9
+	From SUBSCRIBING to READY via 4
+	From LOADING_OFFLINE to SUBSCRIBING via 23
+	From - to LOADING_OFFLINE via -
 
 
 
@@ -39,6 +47,8 @@
 	-- expose participant count?: can be gotten via participants.length, only if you are "subscribed" to participant shareds
 	-- expose participant ids, id list
 	-- expose own id
+	-- event when new participant joins or leaves?
+
 
 - Tooling
 	-- maybe jump to esbuild and/or vite?