Directory Client Protocol - Revision history

Doc flabby: added some detail on description max length

2009-05-06T15:08:59Z

added some detail on description max length

← Older revision		Revision as of 15:08, 6 May 2009
Line 25:		Line 25:
	11 4 version (0x86 0x00 0x00 0x00)		11 4 version (0x86 0x00 0x00 0x00)
	15 64 name		15 64 name
	79 ? description		79 ? description (should not be longer than around 480-490 in length)
	packet repeats from offset 1 until end		packet repeats from offset 1 until end
	</pre>		</pre>

2007-10-10T00:28:00Z

added bullet point

← Older revision		Revision as of 00:28, 10 October 2007
Line 30:		Line 30:

	=== See also ===		=== See also ===
	[[Directory Game Server Protocol]]		* [[Directory Game Server Protocol]]

	[[Category: Protocol]]		[[Category: Protocol]]

2006-09-28T17:43:08Z

Also See: renamed g2d link and subheading

← Older revision		Revision as of 17:43, 28 September 2006
Line 29:		Line 29:
	</pre>		</pre>

	=== ~~Also~~ See ===		=== See also ===
	[[~~Server to~~ Directory Server Protocol]]		[[Directory Game Server Protocol]]

	[[Category: Protocol]]		[[Category: Protocol]]

2006-09-28T11:21:01Z

reor

← Older revision		Revision as of 11:21, 28 September 2006
Line 2:		Line 2:

	Continuum sends a sync request and SubSpace doesn't.		Continuum sends a sync request and SubSpace doesn't.
	The list request is sent as reliable. On the traditional directory servers (not catid's), traffic is always encrypted, even if you send a null encryption key.		The list request is sent as reliable. On the traditional directory servers (not [[catid]]'s), traffic is always encrypted, even if you send a null encryption key.

	Directory servers listen on port 4990 for ~~client connections, and 4991 for updates to each zone's data using the~~ [[~~Server to Directory Server Protocol]] as well as pings using the old [[Ping Protocol~~]].		Directory servers listen on port 4990 for [[client]] connections.

	<pre>		<pre>
Line 28:		Line 28:
	packet repeats from offset 1 until end		packet repeats from offset 1 until end
	</pre>		</pre>

			=== Also See ===
			[[Server to Directory Server Protocol]]

	[[Category: Protocol]]		[[Category: Protocol]]

2006-09-28T11:02:58Z

more specific about the ping protocol

← Older revision		Revision as of 11:02, 28 September 2006
Line 4:		Line 4:
	The list request is sent as reliable. On the traditional directory servers (not catid's), traffic is always encrypted, even if you send a null encryption key.		The list request is sent as reliable. On the traditional directory servers (not catid's), traffic is always encrypted, even if you send a null encryption key.

	Directory servers listen on port 4990 for client connections, and 4991 for updates to each zone's data using the [[Server to Directory Server Protocol]] as well as pings using the [[Ping Protocol]].		Directory servers listen on port 4990 for client connections, and 4991 for updates to each zone's data using the [[Server to Directory Server Protocol]] as well as pings using the old [[Ping Protocol]].

	<pre>		<pre>

2006-09-28T10:59:20Z

forgot my wiki markup

← Older revision		Revision as of 10:59, 28 September 2006
Line 4:		Line 4:
	The list request is sent as reliable. On the traditional directory servers (not catid's), traffic is always encrypted, even if you send a null encryption key.		The list request is sent as reliable. On the traditional directory servers (not catid's), traffic is always encrypted, even if you send a null encryption key.

	Directory servers listen on port 4990 for client connections, and 4991 for updates to each zone's data using the [Server to Directory Server Protocol] as well as pings using the [Ping Protocol].		Directory servers listen on port 4990 for client connections, and 4991 for updates to each zone's data using the [[Server to Directory Server Protocol]] as well as pings using the [[Ping Protocol]].

	<pre>		<pre>

2006-09-28T10:58:55Z

expanded to allow new page for directory server <-> server protocol

← Older revision		Revision as of 10:58, 28 September 2006
Line 4:		Line 4:
	The list request is sent as reliable. On the traditional directory servers (not catid's), traffic is always encrypted, even if you send a null encryption key.		The list request is sent as reliable. On the traditional directory servers (not catid's), traffic is always encrypted, even if you send a null encryption key.

	Directory servers listen on port 4990 for client connections, and 4991 for updates to each zone's data ~~and~~ pings.		Directory servers listen on port 4990 for client connections, and 4991 for updates to each zone's data using the [Server to Directory Server Protocol] as well as pings using the [Ping Protocol].

	<pre>		<pre>

2006-09-28T10:57:36Z

encryption note

← Older revision		Revision as of 10:57, 28 September 2006
Line 2:		Line 2:

	Continuum sends a sync request and SubSpace doesn't.		Continuum sends a sync request and SubSpace doesn't.
	The list request is sent as reliable.		The list request is sent as reliable. On the traditional directory servers (not catid's), traffic is always encrypted, even if you send a null encryption key.

	Directory servers listen on port 4990 for client connections, and 4991 for updates to each zone's data and pings.		Directory servers listen on port 4990 for client connections, and 4991 for updates to each zone's data and pings.

2006-09-24T06:18:27Z

pings too!

← Older revision		Revision as of 06:18, 24 September 2006
Line 4:		Line 4:
	The list request is sent as reliable.		The list request is sent as reliable.

	Directory servers listen on port 4990 for client connections, and 4991 for updates to zone's data.		Directory servers listen on port 4990 for client connections, and 4991 for updates to each zone's data and pings.

	<pre>		<pre>

2006-09-24T06:16:20Z

"clinet" connections

← Older revision		Revision as of 06:16, 24 September 2006
Line 4:		Line 4:
	The list request is sent as reliable.		The list request is sent as reliable.

	Directory servers listen on port 4990 for connections, and 4991 for updates to zone's data.		Directory servers listen on port 4990 for client connections, and 4991 for updates to zone's data.

	<pre>		<pre>