1 MONITOR - Protocol for notification of when clients become online/offline
2 Lee Hardy <lee -at- leeh.co.uk>
3 $Id: monitor.txt 26 2006-09-20 18:02:06Z spb $
4 -------------------------------------------------------------------------
6 Currently, ISON requests by clients use a large amount of bandwidth. It is
7 expected that it is more efficient for this to be done by the server at the
8 expense of cpu cycles. The WATCH implementation that was designed to counter
9 this is (in my opinion) severely flawed. This protocol was designed to
10 provide a cleaner implementation.
12 The command used throughout this specification is "MONITOR".
14 Each use of the MONITOR command takes a special modifier, indicating
15 the operation being performed. The client MUST NOT attempt to specify
16 more than one modifier. Only one special modifier may be used per MONITOR
19 Thus it is impossible to combine additions to the list with removals from
20 the list -- these MUST be done with two seperate commands.
22 A client MUST NOT issue the MONITOR command more than once per second.
23 Any attempts to do so will generate an error.
25 In commands and numerics where multiple nicknames may occur, the length of
26 the nickname list is limited only by the buffer size of 512 chars, as
29 Support of this specification is indicated by the MONITOR token in
30 RPL_ISUPPORT (005). This token takes an optional parameter, of the maximum
31 amount of nicknames a client may have in their monitor list. If no
32 parameter is specified, there is no limit. A typical token would be:
35 MONITOR + nick[,nick2]*
36 -----------------------
37 Adds the given list of nicknames to the list of nicknames being monitored.
39 If any of the nicknames being added are online, the server will generate
40 RPL_MONONLINE numerics listing those nicknames that are online.
42 If any of the nicknames being added are offline, the server will generate
43 RPL_MONOFFLINE numerics listing those nicknames that are offline.
45 MONITOR - nick[,nick2]*
46 -----------------------
47 Removes the given list of nicknames from the list of nicknames being
48 monitored. No output will be returned for use of this command.
52 Clears the list of nicknames being monitored. No output will be returned
53 for use of this command.
57 Outputs the current list of nicknames being monitored. All output will use
58 RPL_MONLIST, and the output will be terminated with RPL_ENDOFMONLIST
62 Outputs for each nickname in the list being monitored, whether the client is
63 online or offline. All nicks that are online will be sent using
64 RPL_MONONLINE, all nicks that are offline will be sent using RPL_MONOFFLINE.
65 The list will be terminated with RPL_ENDOFMONLIST.
73 :<server> 730 <nick> :nick!user@host[,nick!user@host]*
75 This numeric is used to indicate to a client that either a nickname has just
76 become online, or that a nickname they have added to their monitor list is
81 :<server> 731 <nick> :nick[,nick1]*
83 This numeric is used to indicate to a client that either a nickname has just
84 left the irc network, or that a nickname they have added to their monitor
87 The argument is a chained list of nicknames that are offline.
91 :<server> 732 <nick> :nick[,nick1]*
93 This numeric is used to indicate to a client the list of nicknames they have
94 in their monitor list.
96 733 - RPL_ENDOFMONLIST
97 ------------------------
98 :<server> 733 <nick> :End of MONITOR list
100 This numeric is used to indicate to a client the end of a monitor list.
102 734 - ERR_MONLISTFULL
103 ---------------------
104 :<server> 734 <nick> <limit> <nicks> :Monitor list is full.
106 This numeric is used to indicate to a client that their monitor list is
107 full, so the command failed. The <limit> parameter is the maximum number of
108 nicknames a client may have in their list, the <nicks> parameter is the list
109 of nicknames, as the client sent them, that cannot be added.