Notifies the client of an event. These events are intended for sysops and sysop managers, and are sent in addition to IRC events.
Syntax:
:<server> EVENT <time-stamp> <object> <event type> <parameters>
<time-stamp> The number of elapsed seconds from midnight (00:00:00) January 1, 1970 (coordinated universal time) until the time that the event occurred on the server.
<object> Objects can be Channel, Member, User, Connection, Socket or Server.
<event type> Event type varies depending on the object. For example, events for channels can be Create, Destroy, Topic change, Mode change, Collision.
<parameters> Vary depending on event type.
This example is the event generated when a user logs onto server, "chat1" with the nickname, "john", showing the user's info including IP address and port.
Example 4.3. Event generated when a user logs on
Server: :chat1 EVENT 946080000 USER LOGON john!jsmith@uw.edu 192.29.93.93:1111
(note that this isn't the set of parameters for reporting a user logon that is supported in Microsoft Exchange - since there is no standard set of parameters, each vendor could do their parameters differently, and you are free to do so)
![[Note]](images/note.png) | Editor's Note |
|---|---|
Again, the IRCX draft does not specify whether or not a prefix should be expected for this command. Through various tests, it seems it would be okay to assume that IRCX clients do expect a prefix for this command. Server developers should send a prefix to maintain proper support for RFC 1459. However, client developers should expect this command with and without a prefix. | |