Author: dylan
Date: 2004-07-02 01:38:33 -0400 (Fri, 02 Jul 2004)
New Revision: 286
Modified:
trunk/docs/protocol/commands.txt
Log:
Introduced OF, don't worry about this, yet.
Modified: trunk/docs/protocol/commands.txt
===================================================================
--- trunk/docs/protocol/commands.txt 2004-07-01 23:39:00 UTC (rev 285)
+++ trunk/docs/protocol/commands.txt 2004-07-02 05:38:33 UTC (rev 286)
@@ -17,14 +17,14 @@
At this point the server WANTs a uid,
but doesn't send anything other than the 'REJECT'.
-IN $cid JOIN $uid
- $uid joined the channel $cid.
+JOIN
+ current $IN joined current $OF.
-IN $cid PART $uid
+PART
opposite of JOIN; the user has left $cid.
-QUIT $uid $type [$detail]
- $uid left the server.
+QUIT $type [$detail]
+ $OF left the server.
$type is one of:
ACTIVE
DIE
@@ -42,23 +42,15 @@
Like QUIT, except the client is the one
that is leaving.
-IN $cid $cmd
- In single channel mode, this is only used if the
- client has sent 'IN'.
-
- IN is always sent in multi channel mode for any command
- that requires it (such as USERS or MSG).
-
- The client should note the $cid and process $cmd
- as if it were a normal command (see below)
+IN $cid $cmd [$args...]
+ The client should note the $cid and process $cmd.
-IN $cid MSG $uid $type $msg
- Public message from $uid in the current channel.
- IN may only be used in multi-channel mode.
+OF $uid $cmd [$args...]
+ The client should note the $uid and process $cmd.
+
+MSG $type $msg...
+ A message.
-MSG $uid $type $msg
- Private message from $uid.
-
WARN $error [$data1] [$data2] [$data#...]
Warns of $error, optionally followed
by any number of extra bits of data, such as uids or cids.
