[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[or-cvs] note GETCONF default feature in spec



Update of /home/or/cvsroot/tor/doc
In directory moria:/tmp/cvs-serv11588/doc

Modified Files:
	control-spec.txt 
Log Message:
note GETCONF default feature in spec

Index: control-spec.txt
===================================================================
RCS file: /home/or/cvsroot/tor/doc/control-spec.txt,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -d -r1.41 -r1.42
--- control-spec.txt	19 Jun 2005 20:40:41 -0000	1.41
+++ control-spec.txt	19 Jun 2005 23:22:34 -0000	1.42
@@ -138,6 +138,9 @@
   If all of the listed keywords exist in the Tor configuration, Tor replies
   with a series of reply lines of the form:
       250 keyword=value
+  If any option is set to a 'default' value semantically different from an
+  empty string, Tor may reply with a reply line of the form:
+      250 keyword
 
   If some of the listed keywords can't be found, Tor replies with a
    "552 unknown configuration keyword" message.
@@ -520,6 +523,15 @@
      S: 650 CIRC 1000 EXTENDED moria1,moria2
      S: 250 ORPORT=0
 
+  Clients SHOULD tolerate more arguments in an asynchonous reply than
+  expected, and SHOULD tolerate more lines in an asynchronous reply than
+  expected.  For instance, a client that expects a CIRC message like:
+      650 CIRC 1000 EXTENDED moria1,moria2
+  should tolerate:
+      650+CIRC 1000 EXTENDED moria1,moria2 0xBEEF
+      650-EXTRAMAGIC=99
+      650 ANONYMITY=high
+
 4.1.1 Circuit status changed
 
    The syntax is: