P10 Protocol - Revision history

Nitemare: /* Channels */

2012-06-30T18:42:23Z

Channels

← Older revision		Revision as of 18:42, 30 June 2012
Line 654:		Line 654:
	# [OPTIONAL] '''[arg2]''' - Channel limit, this parameter is present if the channel modes contain a "l" mode.		# [OPTIONAL] '''[arg2]''' - Channel limit, this parameter is present if the channel modes contain a "l" mode.
	# '''<member_list>''' - A comma separated list of client numerics, with the following specific formatting rules to indicate +o, +h, +v and +ohv channel members.		# '''<member_list>''' - A comma separated list of client numerics, with the following specific formatting rules to indicate +o, +h, +v and +ohv channel members.
-	## Numerics can have the following symbols appended on then: ":ohv", ":oh", ":ov", ":hv", ":v", ":h" or ":o". These indicate that this numeric is either opped (:o), halfoped, (:h), voiced (:v) or a combination of the three. This state applies to the numeric it is attached to, and all subsequent numerics until another state is encountered. For example: AAABA:ov. AAABB:o,AAABC,AAABD,AAABE:v,AAABZ. In this example, AAABA is both opped and voiced; AAABB, AAABC and AAABD are opped leaving AAABE and AAABZ voiced.	+	## Numerics can have the following symbols appended on then: ":ohv", ":oh", ":ov", ":hv", ":v", ":h" or ":o". These indicate that this numeric is either opped (:o), halfoped, (:h), voiced (:v) or a combination of the three. This state applies to the numeric it is attached to, and all subsequent numerics until another state is encountered. For example: AAABA:ov,AAABB:o,AAABC,AAABD,AAABE:v,AAABZ. In this example, AAABA is both opped and voiced; AAABB, AAABC and AAABD are opped leaving AAABE and AAABZ voiced.
	## The first numeric of the member list will always contain a state symbol.		## The first numeric of the member list will always contain a state symbol.
	# [OPTIONAL] '''[:%bans [~ excepts]]''' - A space separated list of bans and/or excepts present in the channel. The start of the ban stream is indicated by a ":%', with everything following being the ban list, up until a single "~", which indicates the start of an except stream, with everything following being the except list.		# [OPTIONAL] '''[:%bans [~ excepts]]''' - A space separated list of bans and/or excepts present in the channel. The start of the ban stream is indicated by a ":%', with everything following being the ban list, up until a single "~", which indicates the start of an except stream, with everything following being the except list.

Nitemare: /* Channels */

2012-06-30T18:39:25Z

Channels

← Older revision		Revision as of 18:39, 30 June 2012
Line 654:		Line 654:
	# [OPTIONAL] '''[arg2]''' - Channel limit, this parameter is present if the channel modes contain a "l" mode.		# [OPTIONAL] '''[arg2]''' - Channel limit, this parameter is present if the channel modes contain a "l" mode.
	# '''<member_list>''' - A comma separated list of client numerics, with the following specific formatting rules to indicate +o, +h, +v and +ohv channel members.		# '''<member_list>''' - A comma separated list of client numerics, with the following specific formatting rules to indicate +o, +h, +v and +ohv channel members.
-	## Numerics can have the following symbols appended on then: ":ohv", ":oh", ":ov", ":hv", ":v", ":h" or ":o". These indicate that this numeric is either opped (:o), halfoped, (:h), voiced (:v) or a combination of the three. This state applies to the numeric it is attached to, and all subsequent numerics until another state is encountered. For example: AAABA:ob. AAABB:o,AAABC,AAABD,AAABE:v,AAABZ. In this example, AAABA is both opped and voiced; AAABB, AAABC and AAABD are opped leaving AAABE and AAABZ voiced.	+	## Numerics can have the following symbols appended on then: ":ohv", ":oh", ":ov", ":hv", ":v", ":h" or ":o". These indicate that this numeric is either opped (:o), halfoped, (:h), voiced (:v) or a combination of the three. This state applies to the numeric it is attached to, and all subsequent numerics until another state is encountered. For example: AAABA:ov. AAABB:o,AAABC,AAABD,AAABE:v,AAABZ. In this example, AAABA is both opped and voiced; AAABB, AAABC and AAABD are opped leaving AAABE and AAABZ voiced.
	## The first numeric of the member list will always contain a state symbol.		## The first numeric of the member list will always contain a state symbol.
	# [OPTIONAL] '''[:%bans [~ excepts]]''' - A space separated list of bans and/or excepts present in the channel. The start of the ban stream is indicated by a ":%', with everything following being the ban list, up until a single "~", which indicates the start of an except stream, with everything following being the except list.		# [OPTIONAL] '''[:%bans [~ excepts]]''' - A space separated list of bans and/or excepts present in the channel. The start of the ban stream is indicated by a ":%', with everything following being the ban list, up until a single "~", which indicates the start of an except stream, with everything following being the except list.

Admin: /* Command Token Table */

2012-06-14T20:19:59Z

Command Token Table

← Older revision		Revision as of 20:19, 14 June 2012
Line 29:		Line 29:
	The below table lists all acceptable messages, along with their relevant "token", which is used in server<>server communication. The aim of tokenization is to reduce the bandwidth used during network communication by reducing the total length of common message identifiers.		The below table lists all acceptable messages, along with their relevant "token", which is used in server<>server communication. The aim of tokenization is to reduce the bandwidth used during network communication by reducing the total length of common message identifiers.

-	{\| class="~~widefat~~" width="100%" style="text-align: left;"	+	{\| class="simpletable" width="100%" style="text-align: left;"
	\|-		\|-
-	! style="~~background~~-~~color~~: ~~#333; color: #fff~~;" width="200px"\|Token	+	! style="text-align: left;" width="200px"\|Token
-	! style="~~background~~-~~color: #333; color~~: ~~#fff~~;"\|Command/Message	+	! style="text-align: left;"\|Command/Message
	\|-		\|-

Admin: /* Command Token Table */

2012-06-14T20:17:33Z

Command Token Table

← Older revision		Revision as of 20:17, 14 June 2012
Line 29:		Line 29:
	The below table lists all acceptable messages, along with their relevant "token", which is used in server<>server communication. The aim of tokenization is to reduce the bandwidth used during network communication by reducing the total length of common message identifiers.		The below table lists all acceptable messages, along with their relevant "token", which is used in server<>server communication. The aim of tokenization is to reduce the bandwidth used during network communication by reducing the total length of common message identifiers.

-	{\| class="widefat" width="40%" style="~~font-size: 85%;~~ text-align: left;"	+	{\| class="widefat" width="100%" style="text-align: left;"
	\|-		\|-
	! style="background-color: #333; color: #fff;" width="200px"\|Token		! style="background-color: #333; color: #fff;" width="200px"\|Token

Admin at 10:42, 13 June 2012

2012-06-13T10:42:29Z

Show changes

Admin: /* Continuous Operation */

2010-07-10T15:52:06Z

Continuous Operation

← Older revision		Revision as of 15:52, 10 July 2010
Line 907:		Line 907:
	== Continuous Operation ==		== Continuous Operation ==
	----		----
-	This section provides details of the various messages that can be sent after successfully linking to the network, and ~~synchronizing the channel/user database~~.	+	This section provides details of the various messages that can be sent after successfully linking to the network, and maintaining a synchronized state.

	=== Server State Operations ===		=== Server State Operations ===

Admin: /* SETTIME */

2010-07-10T15:49:51Z

SETTIME

← Older revision		Revision as of 15:49, 10 July 2010
Line 937:		Line 937:

	Syntax:<pre>		Syntax:<pre>
-	1 2	+	1 2
-	<timestamp> [<target_numeric>]</pre>	+	SE <timestamp> [<target_numeric>]</pre>

	* '''<timestamp>''' - An epoch timestamp of the current time.		* '''<timestamp>''' - An epoch timestamp of the current time.

Admin: /* SETTIME */

2010-07-10T15:49:21Z

SETTIME

← Older revision		Revision as of 15:49, 10 July 2010
Line 937:		Line 937:

	Syntax:<pre>		Syntax:<pre>
-	1 1/2	+	1 2
	<timestamp> [<target_numeric>]</pre>		<timestamp> [<target_numeric>]</pre>

Line 944:		Line 944:

	Servers with RELIABLE_CLOCK will change the timestamp parameter of any <code>SETTIME</code> message to its own perception of what the current time is.		Servers with RELIABLE_CLOCK will change the timestamp parameter of any <code>SETTIME</code> message to its own perception of what the current time is.
		+
		+	Example:
		+	<pre>AF SE 1278767962</pre>

	=== Channel State Operations ===		=== Channel State Operations ===

Admin: /* Server State Operations */

2010-07-10T15:47:07Z

Server State Operations

← Older revision		Revision as of 15:47, 10 July 2010
Line 917:		Line 917:
	Removes a server from the network.		Removes a server from the network.

-	~~Parameters~~:<pre>	+	Syntax:<pre>
-	1 2 -1	+	1 2 -1
-	<target> <link_ts> [:reason]</pre>	+	SQ <target> <link_ts> [:<reason>]</pre>

	* '''<target>''' - The name of the target server (not its numeric), without wildcards.		* '''<target>''' - The name of the target server (not its numeric), without wildcards.
Line 931:		Line 931:

	If a <code>SQUIT</code> message is to be sent to a directly linked target, the <target> parameter will be the name of the local server. In this case, ircu sends a link timestamp of 0.		If a <code>SQUIT</code> message is to be sent to a directly linked target, the <target> parameter will be the name of the local server. In this case, ircu sends a link timestamp of 0.
		+
		+	==== SETTIME ====
		+
		+	Sets the "clock" of one or all servers.
		+
		+	Syntax:<pre>
		+	1 1/2
		+	<timestamp> [<target_numeric>]</pre>
		+
		+	* '''<timestamp>''' - An epoch timestamp of the current time.
		+	* [OPTIONAL] '''[<target_numeric>]''' - The numeric of the target server. This parameter is present if an oper issued "/settime <timestamp> <target server numeric>". In which case, the change will only apply to that specific server. If this parameter is not present, the change will be broadcasted to all servers.
		+
		+	Servers with RELIABLE_CLOCK will change the timestamp parameter of any <code>SETTIME</code> message to its own perception of what the current time is.

	=== Channel State Operations ===		=== Channel State Operations ===

Admin: /* Server State Operations */

2010-07-10T15:35:15Z

Server State Operations

← Older revision		Revision as of 15:35, 10 July 2010
Line 910:		Line 910:

	=== Server State Operations ===		=== Server State Operations ===
		+
		+	As discussed earlier, a server object is created when a new server is introduced by means of the <code>SERVER</code> message. A server object is destructed when an <code>SQUIT</code> message is received.
		+
		+	==== SQUIT ====
		+
		+	Removes a server from the network.
		+
		+	Parameters:<pre>
		+	1 2 -1
		+	<target> <link_ts> [:reason]</pre>
		+
		+	* '''<target>''' - The name of the target server (not its numeric), without wildcards.
		+	* '''<link_ts>''' - If the <link_ts> parameter is equal to the link timestamp of the target server, or equal to 0, it applies; otherwise, the <code>SQUIT</code> message is ignored.
		+	* [OPTIONAL] - '''[:reason]''' - An optional reason indicating why the server is being disconnected.
		+
		+	Example:
		+	<pre> AZ SQ server2.darenet.org 1278767962 :Performing updates.</pre>
		+
		+	The message is propagated to all links except the link where the message cam from, and the target server if it is directly linked.
		+
		+	If a <code>SQUIT</code> message is to be sent to a directly linked target, the <target> parameter will be the name of the local server. In this case, ircu sends a link timestamp of 0.

	=== Channel State Operations ===		=== Channel State Operations ===