SESSION LAYER PROTOCOL FOR CITADEL/UX
- (c) 1995-2000 by Art Cancro et. al. All Rights Reserved
+ (c) 1995-2001 by Art Cancro et. al. All Rights Reserved
INTRODUCTION
what you did, so that your new commands can be added to this document.
The coordinator of the Citadel/UX project is Art Cancro
-<ajc@uncnsrd.mt-kisco.ny.us>.
+<ajc@uncensored.citadel.org>.
CONNECTING TO A SERVER
should begin sending a listing of some sort. The client *must* send something,
even if it is an empty listing. Again, the listing ends with "000" on a line
by itself.
-
+ BINARY_FOLLOWS and SEND_BINARY mean that the client must immediately send
+or receive a block of binary data. The first parameter will always be the
+number of bytes.
+ ASYNC_MESSAGE_FOLLOWS means that an asynchronous, or unsolicited, message
+follows. The next line will be one of the above codes, and if a data transfer
+is involved it must be handled immediately. Note that the client will not
+receive this type of response unless it indicates to the server that it is
+capable of handling them; see the writeup of the ASYN command later in this
+document.
PARAMETERIZATION
----------------
your own.
-> Clients other than your own should still be able to utilize your server,
even if your proprietary extensions aren't supported.
- -> Please contact Art Cancro <ajc@uncnsrd.mt-kisco.ny.us> and obtain a unique
+ -> Please contact Art Cancro <ajc@uncensored.citadel.org> and obtain a unique
server type code, which can be assigned to your server program.
-> If you document what you did in detail, perhaps it can be added to a
future release of the Citadel/UX program, so everyone can enjoy it. Better
The server message contained on the same line with LISTING_FOLLOWS will
contain the name of the system and the name of the directory, such as:
- uncnsrd.mt-kisco.ny.us|/usr/bbs/files/my_room_directory
+ uncensored.citadel.org|/usr/bbs/files/my_room_directory
SLRP (Set Last-message-Read Pointer)
- This command is used to mark messages as having been read. Its sole parameter
+ This command marks all messages in the current room as read (seen) up to and
+including the specified number. Its sole parameter
is the number of the last message that has been read. This allows the pointer
to be set at any arbitrary point in the room. Optionally, the parameter
"highest" may be used instead of a message number, to set the pointer to the
Line 8: Telephone number
Line 9: Access level
Line 10: Internet e-mail address
+ Line 11: Country
Users without Aide privileges may retrieve their own registration using
this command. This can be accomplished either by passing the user's own
Line 5: ZIP Code
Line 6: Telephone number
Line 7: e-mail address
+ Line 8: Country
CHEK (CHEcK various things)
Receive from the server a named user's bio. This command should be passed
a single argument - the name of the user whose bio is requested. RBIO returns
-LISTING_FOLLOWS plus the bio file if the user exists and has a bio on file,
-ERROR+NO_SUCH_USER if the named user does not exist, or ERROR+FILE_NOT_FOUND
-if the user exists but has no bio on file.
+LISTING_FOLLOWS plus the bio file if the user exists and has a bio on file.
+The return has the following parameters: the user name, user number, access
+level, date of last call, times called, and messages posted. This command
+returns ERROR+NO_SUCH_USER if the named user does not exist.
+
+ RBIO no longer considers a user with no bio on file to be an error condition.
+It now returns a message saying the user has no bio on file as the text of the
+bio. This allows newer servers to operate with older clients.
STEL (enter STEaLth mode)
a client program is prohibited from terminating the session it is currently
running on.
+ See also: REQT
+
NSET (Network SETup commands)
19. Name of room to log express messages to (or a zero-length name for none)
20. Access level required to create rooms
21. Maximum message length which may be entered into the system
- 22. Default moderation filter level for new users (-63 to +63)
-
-
-
- EXPI (EXPIre system objects)
+ 22. Minimum number of worker threads
+ 23. Maximum number of worker threads
+ 24. Port number for POP3 service
+ 25. Port number for SMTP service
+ 26. Default moderation filter level for new users (-63 to +63)
+ 27. Flag (0 or 1) - allow Aides to zap (forget) rooms
+ 28. Port number for IMAP service
+
+
+ EXPI (EXPIre system objects)
Begins purge operations for objects which, according to site policy, are
"old" and should be removed. EXPI should be called with one argument, one of:
server return code messages, between the return code and the parameters. In
much the same way as FTP uses "-" to signify a continuation, Citadel uses
an "*" in this position to signify the presence of waiting express messages.
-
-
- CICQ (Citadel ICQ metaclient setup)
-
- ** WARNING **
- This command is most likely a temporary one. Citadel will eventually have
-more robust functionality for abstract configuration screens, and when that
-happens, this command will certainly be migrated there. If you're developing
-a client, don't spend a lot of time working on ICQ screens.
-
- If a Citadel server has the ICQ Metaclient installed, this command is used
-to configure it. It has several usages:
-
- CICQ login|uin|pass
-
- This tells Citadel the user's ICQ uin (second argument) and password (third
-argument). When called in this fashion, CICQ will return either OK or ERROR.
-It should be noted, however, that the only way an ERROR code can be returned
-is if the uin and/or password is not supplied. Authentication failures cannot
-be immediately detected, because the ICQ protocol is asynchronous.
-
- CICQ getcl
-
- Request the current contact list. If successful, CICQ will return
-LISTING_FOLLOWS followed by zero or more contacts in the format
-
- uin|nickname|status
-
- CICQ putcl
-
- Upload a new contact list. If successful, CICQ will return SEND_LISTING
-after which the client should transmit zero or more uin's, one per line. The
-server will then attempt to contact the ICQ server to determine nicknames
-and statuses.
-
- CICQ status
-
- Always returns OK followed by a 1 (connected to ICQ) or 0 (not connected).
-
-
-
FSCK (check message base reference counts)
acceptable limits, ERROR+ILLEGAL_VALUE is returned. This command requires at
least Room Aide access; if the calling user is not an Aide, or a Room Aide for
the current room, ERROR+HIGHER_ACCESS_REQUIRED is returned.
+
+
+ REQT (REQuest client Termination)
+
+ Request that the specified client (or all clients) log off. Aide level
+access is required to run this command, otherwise ERROR+HIGHER_ACCESS_REQUIRED
+is returned.
+
+ The REQT command accepts one parameter: the session ID of the client which
+should be terminated, or 0 for all clients. When successful, the REQT command
+returns OK.
+
+ It should be noted that REQT simply transmits an express message to the
+specified client(s) with the EM_GO_AWAY flag set. Older clients do not honor
+this flag, and it is certainly possible for users to re-program their client
+software to ignore it. Therefore the effects of the REQT command should be
+considered advisory only. The recommended implementation practice is to first
+issue a REQT command, then wait a little while (from 30 seconds up to a few
+minutes) for well-behaved clients to voluntarily terminate, and then issue a
+TERM command to forcibly disconnect the client (or perhaps a DOWN command, if
+you are logging off users for the purpose of shutting down the server).
+
+
+ SEEN (set or clear the SEEN flag for a message)
+
+ Beginning with version 5.80, Citadel supports the concept of setting or
+clearing the "seen" flag for each individual message, instead of only allowing
+a "last seen" pointer. In fact, the old semantics are implemented in terms
+of the new semantics. This command requires two arguments: the number of the
+message to be set, and a 1 or 0 to set or clear the "seen" bit.
+
+ This command returns OK, unless the user is not logged in or a usage error
+occurred, in which case it returns ERROR. Please note that no checking is
+done on the supplied data; if the requested message does not exist, the SEEN
+command simply returns OK without doing anything.
+
+
+
+ ASYN (ASYNchronous message support)
+
+ Negotiate the use of asynchronous, or unsolicited, protocol messages. The
+only parameter specified should be 1 or 0 to indicate that the client can or
+cannot handle this type of messages. The server will reply OK followed by a
+1 or 0 to tell the client which mode it is now operating in.
+
+ If the command is not available on the server (i.e. it returns ERROR), or
+if the command has not been executed by the client, it should be assumed that
+this mode of operation is NOT in effect.
+
+ The client may also send any value other than 0 or 1 to simply cause the
+server to output its current state without changing it.
+
+ When asynchronous protocol mode is in effect, the client MUST handle any
+asynchronous messages as they arrive, before doing anything else.
+
+
+
+
+ ASYNCHRONOUS MESSAGES
+ ---------------------
+
+ When the client protocol is operating in asynchronous mode (please refer to
+the writeup of the ASYN command above), the following messages may arrive at
+any time:
+
+
+ 901 (express message arriving)
+
+ There is an express message intended for this client. When the client
+receives this message, it MUST act as if it just sent a GEXP command (the data
+following the 901 message WILL be a LISTING_FOLLOWS data transfer; in fact,
+the current implementation simply executes a GEXP command internally).
projects / citadel.git / blobdiff