From c26830b5f0b17229367019ccb2948ea491ce32a2 Mon Sep 17 00:00:00 2001 From: Pekka Riikonen Date: Wed, 15 Jan 2003 19:23:39 +0000 Subject: [PATCH] Added. --- TODO | 3 - lib/doc/command_reply_args.html | 373 ++++++++++++++++++++++++++++++++ lib/silcclient/DIRECTORY | 7 +- lib/silcclient/silcclient.h | 3 +- 4 files changed, 379 insertions(+), 7 deletions(-) create mode 100644 lib/doc/command_reply_args.html diff --git a/TODO b/TODO index 3b02c089..feead3e0 100644 --- a/TODO +++ b/TODO @@ -34,9 +34,6 @@ TODO in Toolkit Documentation Stuff that needs to be done in order to complete the Tooolkit Reference Manual (Do these to 0.9.x). - o Document the "command_reply" client operations variable - argument lists for all possible notify types and command replys. - o Write "Programming with Toolkit" document, describing how to build Toolkit, how the build system works, where is everything, how new (external) projects can be glued into Toolkit (use irssi as an diff --git a/lib/doc/command_reply_args.html b/lib/doc/command_reply_args.html new file mode 100644 index 00000000..0f781b07 --- /dev/null +++ b/lib/doc/command_reply_args.html @@ -0,0 +1,373 @@ +Command Reply Arguments + +
 
+The SILC Client Library 'command_reply client operation (which is part of the + +SilcClientOperation callback functions) returns command replies +from the SILC Server for commands that the client has earlier sent to the +server. The 'command_reply' client operation implementation has a variable +argument list to deliver SilcCommand +specific arguments to the application. This document describes these +arguments for all command replies to help SILC client software developers +to process them. + +
 
 
+command_reply Client Library operation + +
 
+The 'command_reply' client operation callback function prototype is as follows: + +
 
+ +   +void (*command_reply)(SilcClient client, SilcClientConnection conn,
+          +SilcCommandPayload cmd_payload, bool success, SilcCommand command,
+          +SilcStatus status, ...); + + +
 
+The first argument 'client' is the SILC Client Library context, the 'conn' +is the context for the connection to the remote server, the 'cmd_payload' +is the raw SilcCommandPayload and application usually ignores it, the +'success' boolean value indicates whether the earlier command was a success +or not, the 'command' is the command reply enumeration, and the 'status' +indicates the status of the command reply. If 'success' is FALSE then +'status' includes error status. + +
 
+Rest of the arguments are 'command' specific and implementation should +handle them by the SilcCommand for example in a switch statement. +The commands are defined in lib/silccore/silccomand.h header file. A short +example: + +
 
+ +  switch(type)
+    {
+    case SILC_COMMAND_WHOIS:
+    ...
+    break;
+    case SILC_COMMAND_WHOWAS:
+    ...
+    break;
+    case SILC_COMMAND_NICK:
+    ...
+    break;
+    ...
+    } + + +
 
 
+Arguments + +
 
+The following table describes all commands and arguments that the client +library sends in the 'command_reply' client operation to the application. +By default all arguments that the libary sends to application are valid +pointers. However, it is possible that some pointers may be NULL. If +this is the case it is separately mentioned that the argument may be NULL. +In this case application must ignore that argument. The 'command_reply' +arguments per SilcCommand is as follows: + +
 
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescriptionVariable Arguments
SILC_COMMAND_WHOIS +Returns information about user. The following pointers may be NULL: 'channels', +'fingerprint', 'channel_usermodes' and 'attrs'. If 'fingerprint' is valid its +length is 20 bytes. If 'channels' is valid it can be parsed with +silc_channel_payload_parse_list function. It is the list of channels user +has joined. If the 'channel_usermodes' is valid it can be parsed with +silc_get_mode_list function. It is the list of the user's modes on the +joined channels. The 'attr' is the Requested Attributes that may have been +returned by the client and it can be parsed by traversing the SilcDList +and using silc_attribute_get_attribute function. +SilcClientEntry client_entry, char *nickname, +char *username, char *realname, SilcBuffer channels, SilcUInt32 usermode, +SilcUInt32 idletime, unsigned char *fingerprint, SilcBuffer channel_usermodes, +SilcDList attrs +
SILC_COMMAND_WHOWAS +Returns history information about user. The 'client_entry' and 'realname' +may be NULL. +SilcClientEntry client_entry, char *nickname, +char *username, char *realname +
SILC_COMMAND_IDENTIFY +Returns information about user, channel or server. This is similar to +WHOIS command but does not return so much information and can be used to +get information about channels and servers too. Application should ignore +this command reply. The 'name' and 'info' may be NULL. +void *entry, char *name, char *info +
SILC_COMMAND_NICK +Returns the new Client ID after user has changed nickname. +SilcClientEntry local_entry, char *nickname +
SILC_COMMAND_LIST +Returns the list of channel in the SILC network. Each call of command reply +returns one channel. This means that the command reply is called multiple +times to return list of channels. The 'channel_topic' may be NULL. +SilcChannelEntry channel, char *channel_name, +char *channel_topic, SilcUInt32 user_count +
SILC_COMMAND_TOPIC +Returns the topic of the channel. +SilcChannelEntry channel, char *topic +
SILC_COMMAND_INVITE +Returns the invite list of the channel. Called also even if invite list +was not modified but SILC_COMMAND_INVITE command was used to invite a user +into a channel. In this case the invite list is not returned by the +server and 'invite_list' is NULL. The 'invite_list' is list of +SilcArgumentPayloads. The first 2 bytes are the number of arguments in +the list and can be parsed with SILC_GET16_MSB macro. The list can be +parsed with silc_argument_payload_parse function. +SilcChannelEntry channel, SilcBuffer invite_list +
SILC_COMMAND_KILL +Called after killing a client. There is no arguments to this reply. +none +
SILC_COMMAND_INFO +Returns information about the server user is connected to. +SilcServerEntry server, char *server_name, +char *server_info +
SILC_COMMAND_STATS +Returns network statistics from the server. The 'stats_buffer' of length of +'buffer_length' bytes includes 32-bit integers one after the other each +representing some statistics. The integers can be parsed for example with +SILC_GET32_MSB macro. The integers in the buffer are: starttime, uptime, +local_clients, local_channels, local_serverops, local_routerops, cell_clients, +cell_channels, cell_servers, all_clients, all_channel, all_servers, +all_routers, all_serverops, all_routerops. All integers are always present. +unsigned char *stats_buffer, SilcUInt32 buffer_length +
SILC_COMMAND_PING +Returns reply to earlier ping. There is no arguments to this reply. +none +
SILC_COMMAND_OPER +Returns reply to earlier SILC_COMMAND_OPER command. There is no arguments +to this reply. +none +
SILC_COMMAND_JOIN +Reply received when user joined a channel. The 'ignored' argument can +be ignored by the application. The 'topic' and 'hmac_name' may be NULL. +The 'key_payload' is usually ignored by the application. The 'list_count' +is the number of entries in both 'client_id_list' and 'client_mode_list'. +The 'client_id_list' is a list of clients on the channel and 'client_mode_list' +includes those clients' modes on the channel. If application likes to +resolve information about the clients on the channel it may call +silc_client_get_clients_by_list function and pass the 'client_id_list' as +argument to it. The 'client_mode_list' includes 32-bit integers one after +the other and they are in same order as clients in 'client_mode_list'. +If application resolves the information with silc_client_get_clients_by_list +parsing the 'client_mode_list' is not necessary. +char *channel_name, SilcChannelEntry channel, +SilcUInt32 channel_mode, int ignored, SilcBuffer key_payload, NULL, NULL, +char *topic, char *hmac_name, SilcUInt32 list_count, SilcBuffer client_id_list, +SilcBuffer client_mode_list +
SILC_COMMAND_MOTD +Returns the Message of the Day from the server. The 'motd' may be NULL. +char *motd +
SILC_COMMAND_UMODE +Returns the user mode after changing it. +SilcUInt32 user_mode +
SILC_COMMAND_CMODE +Returns channel's mode after changing it. +SilcChannelEntry channel, SilcUInt32 mode +
SILC_COMMAND_CUMODE +Returns user's mode on channel after changing it. +SilcUInt32 mode, SilcChannelEntry channel +SilcClientEntry target_client +
SILC_COMMAND_KICK +Called after kicking a client. There is no arguments to this reply. +none +
SILC_COMMAND_BAN +Returns channel's ban list. The 'ban_list' may be NULL. The construction +of that list is equivalent to invite list. See description of +SILC_COMMAND_INVITE command reply. +SilcChannelEntry channel, SilcBuffer ban_list +
SILC_COMMAND_DETACH +Called after being detached from the SILC network. There is no arguments +to this reply. +none +
SILC_COMMAND_WATCH +Called after modifying the watch list in the server. There is no arguments +to this reply. +none +
SILC_COMMAND_SILCOPER +Returns reply to earlier SILC_COMMAND_OPER command. There is no arguments +to this reply. +none +
SILC_COMMAND_LEAVE +Called after leaving the channel. +SilcChannelEntry channel +
SILC_COMMAND_USERS +Returns list of users in channel. If application wishes not to parse +the raw lists the channel->user_list hash table is updated before calling +this command reply and application may traverse that table instead of +parssing the raw lists. +SilcChannelEntry channel, SilcUInt32 list_count, +SilcBuffer client_id_list, SilcBuffer client_mode_list +
SILC_COMMAND_GETKEY +Returns public key of client or server. The 'public_key' may be NULL. +The 'entry_type' is used to check what type of pointer the entry' is. For +SILC_ID_CLIENT SilcClientEntry and for SILC_ID_SERVER SilcServerEntry. +SilcIdType entry_type, void *entry, +SilcPublicKey public_key +
+ +
 
+SILC protocol defines some additional commands but command replies to +those commands are not delivered to the application. Only the command +replies listed above are delivered to application. diff --git a/lib/silcclient/DIRECTORY b/lib/silcclient/DIRECTORY index f4626167..84267123 100644 --- a/lib/silcclient/DIRECTORY +++ b/lib/silcclient/DIRECTORY @@ -1,9 +1,10 @@ SILC Client Library diff --git a/lib/silcclient/silcclient.h b/lib/silcclient/silcclient.h index d87dff84..5750bb20 100644 --- a/lib/silcclient/silcclient.h +++ b/lib/silcclient/silcclient.h @@ -527,7 +527,8 @@ typedef struct { message to a specific connection. `conn', however, may be NULL. The `type' indicates the type of the message sent by the library. The application can for example filter the message according the - type. */ + type. The variable argument list is arguments to the formatted + message that `msg' may be. */ void (*say)(SilcClient client, SilcClientConnection conn, SilcClientMessageType type, char *msg, ...); -- 2.43.0