Protocol::IRC - IRC protocol handling
This mix-in class provides a base layer of IRC message handling logic. It allows reading of IRC messages from a string buffer and dispatching them to handler methods on its instance.
Protocol::IRC::Client provides an extension to this logic that may be more convenient for IRC client implementations.
Every incoming message causes a sequence of message handling to occur. First, the message is parsed, and a hash of data about it is created; this is called the hints hash. The message and this hash are then passed down a sequence of potential handlers.
Each handler indicates by return value, whether it considers the message to have been handled. Processing of the message is not interrupted the first time a handler declares to have handled a message. Instead, the hints hash is marked to say it has been handled. Later handlers can still inspect the message or its hints, using this information to decide if they wish to take further action.
A message with a command of
COMMAND will try handlers in following places:
$irc->on_message_COMMAND( $message, \%hints )
$irc->on_message( 'COMMAND', $message, \%hints )
For server numeric replies, if the numeric reply has a known name, it will be attempted first at its known name, before falling back to the numeric if it was not handled. Unrecognised numerics will be attempted only at their numeric value.
Because of the wide variety of messages in IRC involving various types of data the message handling specific cases for certain types of message, including adding extra hints hash items, or invoking extra message handler stages. These details are noted here.
Many of these messages create new events; called synthesized messages. These are messages created by the
Protocol::IRC object itself, to better represent some of the details derived from the primary ones from the server. These events all take lower-case command names, rather than capitals, and will have a
synthesized key in the hints hash, set to a true value. These are dispatched and handled identically to regular primary events, detailed above.
If any handler of the synthesized message returns true, then this marks the primary message handled as well.
When messages arrive they are passed to the appropriate message handling method, which the implementation may define. As well as the message, a hash of extra information derived from or relating to the message is also given.
The following keys will be present in any message hint hash:
Initially false. Will be set to true the first time a handler returns a true value.
Values split from the message prefix; see the
Usually the prefix nick, or the hostname in case the nick isn't defined (usually on server messages).
True if the nick mentioned in the prefix refers to this connection.
Added to this set, will be all the values returned by the message's
named_args method. Some of these values may cause yet more values to be generated.
If the message type defines a
user, as returned by
True if the target name is a user and refers to this connection.
Finally, any key whose name ends in
_name will have a corresponding key added with
_folded suffixed on its name, containing the value casefolded using
casefold_name. This is for the convenience of string comparisons, hash keys, etc..
Informs the protocol implementation that more bytes have been read from the peer. This method will modify the
$buffer directly, and remove from it the prefix of bytes it has consumed. Any bytes remaining should be stored by the caller for next time.
Any messages found in the buffer will be passed, in sequence, to the
Sends a message to the peer from the given
Sends a message to the peer directly from the given arguments.
Shortcut to sending a CTCP message. Sends a PRIVMSG to the given target, containing the given verb and argument string.
Shortcut to sending a CTCP reply. As
send_ctcp but using a NOTICE instead.
The following methods are controlled by the server information given in the
ISUPPORT settings. They use the
isupport required method to query the information required.
$name, folded in case according to the server's
ISUPPORT. Such a folded name will compare using
eq according to whether the server would consider it the same name.
Useful for use in hash keys or similar.
Compares two channel occupant prefix flags, and returns a signed integer to indicate which of them has higher priviledge, according to the server's ISUPPORT declaration. Suitable for use in a
sort() function or similar.
cmp_prefix_flags, but compares channel occupant
MODE command flags.
Converts a channel occupant
MODE flag (such as
o) into a name prefix flag (such as
The inverse of
channel if the given name matches the pattern of names allowed for channels according to the server's
user if not.
Returns true if the given nick refers to that in use by the connection.
The following messages are handled internally by
PING messages are automatically replied to with
PRIVMSG are so similar, they are handled together by synthesized events called
ctcpreply. Depending on the contents of the text, and whether it was supplied in a
PRIVMSG or a
NOTICE, one of these three events will be created.
In all cases, the hints hash will contain a
is_notice key being true or false, depending on whether the original messages was a
NOTICE or a
target_name key containing the message target name, a case-folded version of the name in a
target_name_folded key, and a classification of the target type in a
user target type, it will contain a boolean in
target_is_me to indicate if the target of the message is the user represented by this connection.
channel target type, it will contain a
restriction key containing the channel message restriction, if present.
text messages, it will contain a key
text containing the actual message text.
For either CTCP message type, it will contain keys
ctcp_args with the parsed message. The
ctcp_verb will contain the first space-separated token, and
ctcp_args will be a string containing the rest of the line, otherwise unmodified. This type of message is also subject to a special stage of handler dispatch, involving the CTCP verb string. For messages with
VERB as the verb, the following are tried.
CTCP may stand for either
$irc->on_message_CTCP_VERB( $message, \%hints )
$irc->on_message_CTCP( 'VERB', $message, \%hintss )
$irc->on_message( 'CTCP VERB', $message, \%hints )
Requests the byte string to be sent to the peer
Optional. If supplied, returns an Encode object used to encode or decode the bytes appearing in a
text field of a message. If set, all text strings will be returned, and should be given, as Unicode strings. They will be encoded or decoded using this object.
Optional. If provided, invokes the message handling routine called
$name with the given arguments. A default implementation is provided which simply attempts to invoke a method of the given name, or return false if no method of that name exists.
If an implementation does override this method, care should be taken to ensure that methods are tested for and invoked if present, in addition to any other work the method wishes to perform, as this is the basis by which derived message handling works.
Should return the value of the given
As well as the all-capitals server-supplied fields, the following fields may be requested. Their names are all lowercase and contain underscores, to distinguish them from server-supplied fields.
The mode characters from
The flag characters from
A precompiled regexp that matches any of the prefix flags
A map from mode characters to flag characters
A map from flag characters to mode characters
A 4-element array containing the split portions of
[ $listmodes, $argmodes, $argsetmodes, $boolmodes ]
A precompiled regexp that matches any string beginning with a channel prefix character in
Should return the current nick in use by the connection.
Optional. If supplied, should return the current nick as case-folded by the
casefold_name method. If not provided, this will be performed by case-folding the result from
Paul Evans <firstname.lastname@example.org>