/* * Copyright (C) 2004-2012 George Yunaev gyunaev@ulduzsoft.com * * This library is free software; you can redistribute it and/or modify it * under the terms of the GNU Lesser General Public License as published by * the Free Software Foundation; either version 3 of the License, or (at your * option) any later version. * * This library is distributed in the hope that it will be useful, but WITHOUT * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or * FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public * License for more details. */ /*! * \file libirc_rfcnumeric.h * \author Georgy Yunaev * \version 1.0 * \date 09.2004 * \brief This file defines RFC numeric reply codes, which should be used in * ::event_numeric callback. Every code also has a comment regarding its * arguments. */ #ifndef INCLUDE_IRC_RFCNUMERIC_H #define INCLUDE_IRC_RFCNUMERIC_H /*! \brief 001 Welcome to the Internet Relay Network \!\\@\ * * The server sends replies 001 to 004 to a user upon successful registration. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_WELCOME 001 /*! \brief 002 Your host is \, running version \ * * The server sends replies 001 to 004 to a user upon successful registration. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_YOURHOST 002 /*! \brief 003 This server was created \ * * The server sends replies 001 to 004 to a user upon successful registration. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_CREATED 003 /*! \brief 004 \ \ \ \ * * The server sends replies 001 to 004 to a user upon successful registration. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_MYINFO 004 /*! \brief 005 Try server \, port \ * * Sent by the server to a user to suggest an alternative server. This is often used when the connection is refused because the server is already full. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_BOUNCE 005 /*! \brief 302 :*1\ *( * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_USERHOST 302 /*! \brief 303 :*1\ *( * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_ISON 303 /*! \brief 301 \ :\ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_AWAY 301 /*! \brief 305 :You are no longer marked as being away * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_UNAWAY 305 /*! \brief 306 :You have been marked as being away * * These replies are used with the AWAY command (if allowed). RPL_AWAY is sent to any client sending a PRIVMSG to a client which is away. RPL_AWAY is only sent by the server to which the client is connected. Replies RPL_UNAWAY and RPL_NOWAWAY are sent when the client removes and sets an AWAY message. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_NOWAWAY 306 /*! \brief 311 \ \ \ * :\ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_WHOISUSER 311 /*! \brief 312 \ \ :\ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_WHOISSERVER 312 /*! \brief 313 \ :is an IRC operator * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_WHOISOPERATOR 313 /*! \brief 317 \ \ :seconds idle * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_WHOISIDLE 317 /*! \brief 318 \ :End of WHOIS list * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_ENDOFWHOIS 318 /*! \brief 319 " :*( ( "\@" / "+" ) \ " " )" * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_WHOISCHANNELS 319 /*! \brief 314 \ \ \ * :\ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_WHOWASUSER 314 /*! \brief 369 \ :End of WHOWAS * * When replying to a WHOWAS message, a server MUST use the replies RPL_WHOWASUSER, RPL_WHOISSERVER or ERR_WASNOSUCHNICK for each nickname in the presented list. At the end of all reply batches, there MUST be RPL_ENDOFWHOWAS (even if there was only one reply and it was an error). * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_ENDOFWHOWAS 369 /*! \brief 322 \ \<# visible\> :\ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_LIST 322 /*! \brief 323 :End of LIST * * Replies RPL_LIST, RPL_LISTEND mark the actual replies with data and end of the server's response to a LIST command. If there are no channels available to return, only the end reply MUST be sent. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_LISTEND 323 /*! \brief 325 \ \ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_UNIQOPIS 325 /*! \brief 324 \ \ \ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_CHANNELMODEIS 324 /*! \brief 331 \ :No topic is set * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_NOTOPIC 331 /*! \brief 332 \ :\ * * When sending a TOPIC message to determine the channel topic, one of two replies is sent. If the topic is set, RPL_TOPIC is sent back else RPL_NOTOPIC. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_TOPIC 332 /*! \brief 341 \ \ * * Returned by the server to indicate that the attempted INVITE message was successful and is being passed onto the end client. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_INVITING 341 /*! \brief 342 \ :Summoning user to IRC * * Returned by a server answering a SUMMON message to indicate that it is summoning that user. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_SUMMONING 342 /*! \brief 346 \ \ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_INVITELIST 346 /*! \brief 347 \ :End of channel invite list * * When listing the 'invitations masks' for a given channel, a server is required to send the list back using the RPL_INVITELIST and RPL_ENDOFINVITELIST messages. A separate RPL_INVITELIST is sent for each active mask. After the masks have been listed (or if none present) a RPL_ENDOFINVITELIST MUST be sent. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_ENDOFINVITELIST 347 /*! \brief 348 \ \ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_EXCEPTLIST 348 /*! \brief 349 \ :End of channel exception list * * When listing the 'exception masks' for a given channel, a server is required to send the list back using the RPL_EXCEPTLIST and RPL_ENDOFEXCEPTLIST messages. A separate RPL_EXCEPTLIST is sent for each active mask. After the masks have been listed (or if none present) a RPL_ENDOFEXCEPTLIST MUST be sent. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_ENDOFEXCEPTLIST 349 /*! \brief 351 \.\ \ :\ * * Reply by the server showing its version details. The \ is the version of the software being used (including any patchlevel revisions) and the \ is used to indicate if the server is running in "debug mode". The "comments" field may contain any comments about the version or further version details. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_VERSION 351 /*! \brief 352 \ \ \ \ \ ( "H * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_WHOREPLY 352 /*! \brief 315 \ :End of WHO list * * The RPL_WHOREPLY and RPL_ENDOFWHO pair are used to answer a WHO message. The RPL_WHOREPLY is only sent if there is an appropriate match to the WHO query. If there is a list of parameters supplied with a WHO message, a RPL_ENDOFWHO MUST be sent after processing each list item with \ being the item. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_ENDOFWHO 315 /*! \brief 353 ( "= * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_NAMREPLY 353 /*! \brief 366 \ :End of NAMES list * * To reply to a NAMES message, a reply pair consisting of RPL_NAMREPLY and RPL_ENDOFNAMES is sent by the server back to the client. If there is no channel found as in the query, then only RPL_ENDOFNAMES is returned. The exception to this is when a NAMES message is sent with no parameters and all visible channels and contents are sent back in a series of RPL_NAMEREPLY messages with a RPL_ENDOFNAMES to mark the end. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_ENDOFNAMES 366 /*! \brief 364 \ \ :\ \ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_LINKS 364 /*! \brief 365 \ :End of LINKS list * * In replying to the LINKS message, a server MUST send replies back using the RPL_LINKS numeric and mark the end of the list using an RPL_ENDOFLINKS reply. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_ENDOFLINKS 365 /*! \brief 367 \ \ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_BANLIST 367 /*! \brief 368 \ :End of channel ban list * * When listing the active 'bans' for a given channel, a server is required to send the list back using the RPL_BANLIST and RPL_ENDOFBANLIST messages. A separate RPL_BANLIST is sent for each active banmask. After the banmasks have been listed (or if none present) a RPL_ENDOFBANLIST MUST be sent. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_ENDOFBANLIST 368 /*! \brief 371 :\ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_INFO 371 /*! \brief 374 :End of INFO list * * A server responding to an INFO message is required to send all its 'info' in a series of RPL_INFO messages with a RPL_ENDOFINFO reply to indicate the end of the replies. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_ENDOFINFO 374 /*! \brief 375 :- \ Message of the day - * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_MOTDSTART 375 /*! \brief 372 :- \ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_MOTD 372 /*! \brief 376 :End of MOTD command * * When responding to the MOTD message and the MOTD file is found, the file is displayed line by line, with each line no longer than 80 characters, using RPL_MOTD format replies. These MUST be surrounded by a RPL_MOTDSTART (before the RPL_MOTDs) and an RPL_ENDOFMOTD (after). * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_ENDOFMOTD 376 /*! \brief 381 :You are now an IRC operator * * RPL_YOUREOPER is sent back to a client which has just successfully issued an OPER message and gained operator status. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_YOUREOPER 381 /*! \brief 382 \ :Rehashing * * If the REHASH option is used and an operator sends a REHASH message, an RPL_REHASHING is sent back to the operator. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_REHASHING 382 /*! \brief 383 You are service \ * * Sent by the server to a service upon successful registration. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_YOURESERVICE 383 /*! \brief 391 \ :\ * * When replying to the TIME message, a server MUST send the reply using the RPL_TIME format above. The string showing the time need only contain the correct day and time there. There is no further requirement for the time string. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_TIME 391 /*! \brief 392 :UserID Terminal Host * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_USERSSTART 392 /*! \brief 393 :\ \ \ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_USERS 393 /*! \brief 394 :End of users * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_ENDOFUSERS 394 /*! \brief 395 :Nobody logged in * * If the USERS message is handled by a server, the replies RPL_USERSTART, RPL_USERS, RPL_ENDOFUSERS and RPL_NOUSERS are used. RPL_USERSSTART MUST be sent first, following by either a sequence of RPL_USERS or a single RPL_NOUSER. Following this is RPL_ENDOFUSERS. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_NOUSERS 395 /*! \brief 200 Link \ \ \ V\ \ \ \ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_TRACELINK 200 /*! \brief 201 Try. \ \ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_TRACECONNECTING 201 /*! \brief 202 H.S. \ \ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_TRACEHANDSHAKE 202 /*! \brief 203 ???? \ [\] * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_TRACEUNKNOWN 203 /*! \brief 204 Oper \ \ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_TRACEOPERATOR 204 /*! \brief 205 User \ \ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_TRACEUSER 205 /*! \brief 206 Serv \ \S \C \ \\@\ V\ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_TRACESERVER 206 /*! \brief 207 Service \ \ \ \ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_TRACESERVICE 207 /*! \brief 208 \ 0 \ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_TRACENEWTYPE 208 /*! \brief 209 Class \ \ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_TRACECLASS 209 /*! \brief 261 File \ \ * * No description available in RFC * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_TRACELOG 261 /*! \brief 262 \ \ :End of TRACE * * The RPL_TRACE* are all returned by the server in response to the TRACE message. How many are returned is dependent on the TRACE message and whether it was sent by an operator or not. There is no predefined order for which occurs first. Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and RPL_TRACEHANDSHAKE are all used for connections which have not been fully established and are either unknown, still attempting to connect or in the process of completing the 'server handshake'. RPL_TRACELINK is sent by any server which handles a TRACE message and has to pass it on to another server. The list of RPL_TRACELINKs sent in response to a TRACE command traversing the IRC network should reflect the actual connectivity of the servers themselves along that path. RPL_TRACENEWTYPE is to be used for any connection which does not fit in the other categories but is being displayed anyway. RPL_TRACEEND is sent to indicate the end of the list. * * \ingroup rfcnumbers */ #define LIBIRC_RFC_RPL_TRACEEND 262 /*! \brief 211 \ \ \ \ \ \ \