Commit d1d680fa authored by Per Cederqvist's avatar Per Cederqvist
Browse files

(query-async): Added a reference to the currently preselected

	asynchronous messages, since the example is valid for lyskomd
	1.9 but not lyskomd 2.0.
(Asynchronous Messages): Encourage clients to use accept-async instead
	of trusting the defaults.  State that the obsolete calls may
	be non-existing.
parent 807154c0
\input texinfo @c -*-texinfo-*- \input texinfo @c -*-texinfo-*-
@c $Id: Protocol-A.texi,v 1.32 1998/08/31 17:21:54 ceder Exp $ @c $Id: Protocol-A.texi,v 1.33 1998/10/06 07:39:01 ceder Exp $
@c %**start of header @c %**start of header
@setfilename protocol-a.info @setfilename protocol-a.info
@settitle LysKOM Protocol A @settitle LysKOM Protocol A
...@@ -2553,7 +2553,7 @@ in the example. ...@@ -2553,7 +2553,7 @@ in the example.
* get-info:: Get server information (94) * get-info:: Get server information (94)
* modify-system-info:: Add or delete conference aux items (95) * modify-system-info:: Add or delete conference aux items (95)
* query-predefined-aux-items:: Get list of aux-items the server knows (96) * query-predefined-aux-items:: Get list of aux-items the server knows (96)
* set-expire:: Set the expire field in of conference (97) * set-expire:: Set the expire field of a conference (97)
* query-read-texts:: Get info on what is read (98) * query-read-texts:: Get info on what is read (98)
* get-membership:: Get membership for a person (99) * get-membership:: Get membership for a person (99)
* add-member:: Add a member to a conference (100) * add-member:: Add a member to a conference (100)
...@@ -6115,8 +6115,9 @@ certain circumstances. ...@@ -6115,8 +6115,9 @@ certain circumstances.
In this example the client is receiving seven types of asynchronous In this example the client is receiving seven types of asynchronous
messages: messages about new articles, changed names, database synching, messages: messages about new articles, changed names, database synching,
new logins, rejected connections, personal messages and logouts. This new logins, rejected connections, personal messages and logouts. This
particular set is the default for new connections to lyskomd 1.9 particular set was the default for new connections to lyskomd 1.9
servers. servers. @xref{Asynchronous Messages}, for the currently recommended
list of asynchronous messages that servers should preselect.
@unnumberedsubsubsec Error codes @unnumberedsubsubsec Error codes
...@@ -6974,11 +6975,12 @@ from a person with admin bits set may get through even if the client has ...@@ -6974,11 +6975,12 @@ from a person with admin bits set may get through even if the client has
not requests broadcast messages. not requests broadcast messages.
When a connection is opened some messages are selected by default. When a connection is opened some messages are selected by default.
Specifically, the @code{new-text-old}, @code{new-name}, @code{sync-db}, Clients should use the @code{@ref{accept-async}} call to select which
@code{leave-conf}, @code{login}, @code{rejected-connection}, messages they want. Servers are encouraged to preselect the
@code{send-message} and @code{logout} messages are preselected. These @code{new-text-old}, @code{new-name}, @code{sync-db}, @code{leave-conf},
correspond to the useful messages that were sent prior to the @code{login}, @code{rejected-connection}, @code{send-message} and
introduction of @code{accept-async}. @code{logout} messages. These correspond to the useful messages that
were sent prior to the introduction of @code{accept-async}.
An asynchronous message is sent as a colon immediately followed by the An asynchronous message is sent as a colon immediately followed by the
number of message parameters, the message numbers and the message number of message parameters, the message numbers and the message
...@@ -6989,7 +6991,12 @@ parameters. For example, message number 5 could be sent as ...@@ -6989,7 +6991,12 @@ parameters. For example, message number 5 could be sent as
@end example @end example
The parameters of each message are listed in the same format as server The parameters of each message are listed in the same format as server
calls. calls.
The messages with status "O" are included here for historical purposes
only. Servers are not required to handle them, and are encouraged to
reject them if a client uses it as an argument to
@code{@ref{accept-async}}.
@menu @menu
Message Name Status Description Number Message Name Status Description Number
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment