summaryrefslogtreecommitdiffhomepage
path: root/doc/todo/only_let_one_developer_type_at_a_time.mdwn
diff options
context:
space:
mode:
authorJoey Hess <joeyh@joeyh.name>2017-05-01 12:09:25 -0400
committerJoey Hess <joeyh@joeyh.name>2017-05-01 12:09:25 -0400
commitdc9f329dd64dc0f9c81aac239d66eb0ff9705f7c (patch)
tree02976a0737448b50fc776ab15ecda2476ac10580 /doc/todo/only_let_one_developer_type_at_a_time.mdwn
parenta8b3929082398cdeff56f92f6778744064c7d0b4 (diff)
downloaddebug-me-dc9f329dd64dc0f9c81aac239d66eb0ff9705f7c.tar.gz
move low priority todos to web site
Diffstat (limited to 'doc/todo/only_let_one_developer_type_at_a_time.mdwn')
-rw-r--r--doc/todo/only_let_one_developer_type_at_a_time.mdwn20
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/todo/only_let_one_developer_type_at_a_time.mdwn b/doc/todo/only_let_one_developer_type_at_a_time.mdwn
new file mode 100644
index 0000000..0704bac
--- /dev/null
+++ b/doc/todo/only_let_one_developer_type_at_a_time.mdwn
@@ -0,0 +1,20 @@
+Two developers can connect to a session if the user accepts them both,
+and then they can type at the same time.
+
+debug-me will reject some keystrokes depending on what the other developer
+is doing. This is probably a bit confusing, and it could be a way to
+plausibly deny a bad action, making it look like it was caused by an
+inaverdant mix up of two developers typing.
+
+Better would be to only let one developer type at a time, and they have
+to pass the typing stick to let the other developer type.
+
+Problem: What if one developer has the baton and disconnects? It should
+pass to the other developer, but disconnection does not currently
+cause a protocol message.
+
+Also, related problem, one developer has the baton and goes away,
+still connected.
+
+Seems that perhaps the user needs a way to switch control to another
+developer.