CLONE (new IRCX message)

CLONE (new IRCX message)
Prev	Chapter 4. IRCX Server Messages	Next

Informs the hosts and owners in a CLONEABLE channel that a new CLONE channel was created.

Syntax: CLONE <channel-name> <oid>

Parameters

<channel-name> The name of the created CLONE channel.

<oid> The object identifier for this new CLONE channel. The value is implementation-dependent and must equal 0 if not supported.

Remarks

The CLONE message can be sent at anytime to the hosts/owners of a CLONEABLE channel to inform them that a new CLONE channel was created. This message is intended to be used by a custom application to automatically join the new CLONE channel. A non-IRCX client will not get this message.

Example

Example 4.1. A clone of #MyChat is created

Server: :<server> CLONE #MyChat1 034F8FF32

	Editor's Note
The IRCX draft does not say if the server's prefix comes before the CLONE message (as shown in the example). It can be assumed that it should, because RFC 1459 requires all commands begin with a prefix, except for PING/PONG. IRCX requires that AUTH not have a prefix, because AUTH happens before registering as a user. Client developers should expect to see CLONE with and without a prefix, because the IRCX draft is unclear whether or not it requires a prefix. Server developers should send the message with a prefix in order to follow the IRC RFC.

Editor's Note

The IRCX draft does not say if the server's prefix comes before the CLONE message (as shown in the example). It can be assumed that it should, because RFC 1459 requires all commands begin with a prefix, except for PING/PONG. IRCX requires that AUTH not have a prefix, because AUTH happens before registering as a user.

Client developers should expect to see CLONE with and without a prefix, because the IRCX draft is unclear whether or not it requires a prefix. Server developers should send the message with a prefix in order to follow the IRC RFC.