about summary refs log tree commit homepage
path: root/Documentation/dtas-player_protocol.txt
diff options
context:
space:
mode:
authorEric Wong <normalperson@yhbt.net>2013-08-27 20:23:17 +0000
committerEric Wong <normalperson@yhbt.net>2013-08-27 20:23:17 +0000
commit0d4cafa1cfbd379144b4236343a1e6f2c7f85951 (patch)
treeefa1298fdf6e32ac3bc7d30bf2e9948762312291 /Documentation/dtas-player_protocol.txt
parent4679d5f1012c4e0de28fee9fff0f3edddf1bc74f (diff)
downloaddtas-0d4cafa1cfbd379144b4236343a1e6f2c7f85951.tar.gz
Better to break compatibility while the project is very young.
Diffstat (limited to 'Documentation/dtas-player_protocol.txt')
-rw-r--r--Documentation/dtas-player_protocol.txt19
1 files changed, 19 insertions, 0 deletions
diff --git a/Documentation/dtas-player_protocol.txt b/Documentation/dtas-player_protocol.txt
index 07d14ec..f92f151 100644
--- a/Documentation/dtas-player_protocol.txt
+++ b/Documentation/dtas-player_protocol.txt
@@ -7,6 +7,25 @@ dtas-player_protocol - protocol for controling dtas-player
 
 # DESCRIPTION
 
+NOTE - NOTE - NOTE - NOTE - NOTE - NOTE - NOTE - NOTE
+
+I'm considering a heavy revamp of this protocol.  The "OK" responses for
+a lot of commands may not be necessary since this is Unix sockets and
+not TCP, and I may move away from a request-response model and towards
+an entirely listen/notification model.  I have little experience in
+non-TCP-based application protocols, so this is an area of
+experimentation for me.
+
+This must stay over Unix sockets because filesystem permissions are
+needed to enforce code execution permissions.  dtas-player is really a
+shell in disguise, after all.
+
+Protocol feedback greatly appreciated email me at
+
+normalperson@yhbt.net
+
+*********************************************************
+
 This gives a specification of the dtas-player protocol over a local Unix
 SOCK_SEQPACKET socket.  The dtas-player protocol should NOT be
 considered stable at this point and compatibility will break.