ENCAP Specification
m (→Definition) |
|||
| Line 11: | Line 11: | ||
<pre>:<source> ENCAP <destination> <subcommand> <parameters></pre> | <pre>:<source> ENCAP <destination> <subcommand> <parameters></pre> | ||
| - | *<source> - The entity generating the command. | + | *<nowiki><source></nowiki> - The entity generating the command. |
*<destination> - The entity the command is destined for. This may include wildcards for servers, but not clients. If the wildcard does not match the current server, the command should be propagated and ignored. | *<destination> - The entity the command is destined for. This may include wildcards for servers, but not clients. If the wildcard does not match the current server, the command should be propagated and ignored. | ||
Current revision as of 06:06, 5 February 2009
This document defines the specification for the ENCAP command.
ENCAP is designed to help fix the situation where new commands do not propagate over hub servers running older code.
Definition
Support for the ENCAP command is given by the CAPAB token "ENCAP".
The format of ENCAP is:
:<source> ENCAP <destination> <subcommand> <parameters>
- <source> - The entity generating the command.
- <destination> - The entity the command is destined for. This may include wildcards for servers, but not clients. If the wildcard does not match the current server, the command should be propagated and ignored.
- <subcommand> - The subcommand we're propagating over ENCAP. If the subcommand is not recognised by the current server, the command should be propagated and ignored.
- <parameters> - The parameters that the subcommand have.
