Author: dylan
Date: 2005-03-27 00:49:37 -0500 (Sun, 27 Mar 2005)
New Revision: 658
Modified:
trunk/
trunk/docs/manual/chap/events/connection.texi
trunk/docs/manual/messages.texi
Log:
[EMAIL PROTECTED]: dylan | 2005-03-26 03:01:26 -0500
More additions... Hmm, I need to find a good way of documenting WANT stuff.
Actually I need to think hard about the WANT stuff.
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 1f59643a-e6e5-0310-bc24-f7d4c744f460:/haver/local/trunk:11166
1f59643a-e6e5-0310-bc24-f7d4c744f460:/haver/local/trunk-merge-10131:11178
27e50396-46e3-0310-8b22-ae223a1f35ce:/local:212
e9404bb1-7af0-0310-a7ff-e22194cd388b:/haver/local:867
edfcd8bd-4ce7-0310-a97e-bb1efd40edf3:/local:238
+ 1f59643a-e6e5-0310-bc24-f7d4c744f460:/haver/local/trunk:11166
1f59643a-e6e5-0310-bc24-f7d4c744f460:/haver/local/trunk-merge-10131:11178
27e50396-46e3-0310-8b22-ae223a1f35ce:/local:212
e9404bb1-7af0-0310-a7ff-e22194cd388b:/haver/local:868
edfcd8bd-4ce7-0310-a97e-bb1efd40edf3:/local:238
Modified: trunk/docs/manual/chap/events/connection.texi
===================================================================
--- trunk/docs/manual/chap/events/connection.texi 2005-03-27 05:49:35 UTC
(rev 657)
+++ trunk/docs/manual/chap/events/connection.texi 2005-03-27 05:49:37 UTC
(rev 658)
@@ -15,25 +15,6 @@
The parameters of @command{WANT} events
can vary depending on the value of @var{cmd},
as explain in the following table.
-
-
[EMAIL PROTECTED] @command
[EMAIL PROTECTED] IDENT
[EMAIL PROTECTED] will be empty.
[EMAIL PROTECTED] AUTH
[EMAIL PROTECTED] will be a list of acceptable authorization methods.
[EMAIL PROTECTED] AUTH:PASS
[EMAIL PROTECTED] will contain one item: the hashing method
-the client must use in its @command{AUTH:PASS} event.
-
-Typically it will be SHA-1
-or a function related to the SHA family of hash functions,
-such as SHA-256. However other hash functions are possible.
-
-The canonical hash function is ``sha1''.
-
[EMAIL PROTECTED] table
-
@end deffn
@c *************************************
Modified: trunk/docs/manual/messages.texi
===================================================================
--- trunk/docs/manual/messages.texi 2005-03-27 05:49:35 UTC (rev 657)
+++ trunk/docs/manual/messages.texi 2005-03-27 05:49:37 UTC (rev 658)
@@ -22,9 +22,9 @@
describes how to disconnect, and ways for both the server
and client of making sure the connection is alive.
[EMAIL PROTECTED] *************************************
[EMAIL PROTECTED] ########################################################
[EMAIL PROTECTED] {Client Event} HAVER client
[EMAIL PROTECTED] {Client Message} HAVER client
@mustSendOnce
This event @strong{must} be the first event sent by the client.
@@ -41,11 +41,10 @@
by sending @cmd{HAVER} and @cmd{WANT IDENT}.
@end deffn
[EMAIL PROTECTED]
[EMAIL PROTECTED] *************************************
[EMAIL PROTECTED] ########################################################
[EMAIL PROTECTED] {Server Event} HAVER server
[EMAIL PROTECTED] {Server Message} HAVER server
This event is sent after the client sends @cmd{HAVER}.
The parameter @param{server} is name and version number of the server,
for example ``Haver::Server::POE/0.07''. This is the same form as
@@ -54,4 +53,16 @@
The client can just ignore this.
@end deffn
[EMAIL PROTECTED] ########################################################
[EMAIL PROTECTED] {Server Message} WANT cmd [EMAIL PROTECTED]
+
+When the server sends this message, the client
[EMAIL PROTECTED] either reply with @cmd{cmd}
+or [EMAIL PROTECTED] @param{cmd}''.
+
+If the client sends any other message(s), the server @strong{must} disconnect
+the client.
[EMAIL PROTECTED] deffn
+
+
