summaryrefslogtreecommitdiffhomepage
path: root/doc/todo/only_let_one_developer_type_at_a_time.mdwn
blob: 0704bac797a02c8fd0f9e2eeaf1d4605e1ba8de2 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
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.