Author: dylan
Date: 2004-11-27 12:47:52 -0500 (Sat, 27 Nov 2004)
New Revision: 410
Modified:
trunk/docs/manual/chap/events/channel.texi
trunk/docs/manual/chap/events/connection.texi
Log:
doc change.
Modified: trunk/docs/manual/chap/events/channel.texi
===================================================================
--- trunk/docs/manual/chap/events/channel.texi 2004-10-26 16:01:16 UTC (rev
409)
+++ trunk/docs/manual/chap/events/channel.texi 2004-11-27 17:47:52 UTC (rev
410)
@@ -11,8 +11,8 @@
@strong{Errors:}
@itemize @bullet
[EMAIL PROTECTED] unknown.cid
[EMAIL PROTECTED] syntax.cid
[EMAIL PROTECTED] unknown.channel
[EMAIL PROTECTED] syntax.id
@end itemize
Modified: trunk/docs/manual/chap/events/connection.texi
===================================================================
--- trunk/docs/manual/chap/events/connection.texi 2004-10-26 16:01:16 UTC
(rev 409)
+++ trunk/docs/manual/chap/events/connection.texi 2004-11-27 17:47:52 UTC
(rev 410)
@@ -93,9 +93,10 @@
@strong{Errors:}
@itemize @bullet
[EMAIL PROTECTED] unsupported.mode
[EMAIL PROTECTED] unknown.mode
@item reserved.id
@item used.id
[EMAIL PROTECTED] syntax.id
@end itemize
@end deffn
@@ -112,7 +113,7 @@
Typically, @var{method} will be ``PASS'', but other authorization
methods may be supported in the future.
-The server will issue @command{WANT WANT:foo}
+The server will issue @command{WANT AUTH:foo}
where ``foo'' is @var{method}.
@strong{Errors:}
@@ -167,22 +168,22 @@
The following table lists the different types of client disconnections.
@table @i
[EMAIL PROTECTED] ACTIVE
[EMAIL PROTECTED] active
This is sent when the client has issued the server @command{BYE} event.
The @var{args} may contain a single item, which
is describes the reason for the disconnection. For example,
``lost terminal'', ``reboot'', ``crash'', etc.
[EMAIL PROTECTED] DISCON
[EMAIL PROTECTED] discon
The socket was closed. @var{args} might contain more information.
[EMAIL PROTECTED] TIMEOUT
[EMAIL PROTECTED] timeout
This means the client did not complete the login procedure
fast enough. Typically, the login procedure must be completed in
20 seconds from login, however this can be different depending on server.
[EMAIL PROTECTED] PING
[EMAIL PROTECTED] ping
The client did not respond to a @command{PING}
in time.
@end table
