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

2007-10-10T00:28:00Z

added bullet point

2006-09-28T17:43:08Z

‎Also See: renamed g2d link and subheading

2006-09-28T11:21:01Z

reor

2006-09-28T11:02:58Z

more specific about the ping protocol

2006-09-28T10:59:20Z

forgot my wiki markup

2006-09-28T10:58:55Z

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

2006-09-28T10:57:36Z

encryption note

2006-09-24T06:18:27Z

pings too!

2006-09-24T06:16:20Z

"clinet" connections

@@ Line 25: / Line 25: @@
      4    version (0x86 0x00 0x00 0x00)
      64   name
-     ?    description
+     ?    description (should not be longer than around 480-490 in length)
 packet repeats from offset 1 until end
 </pre>

@@ Line 30: / Line 30: @@
 === See also ===
-[[Directory Game Server Protocol]]
+* [[Directory Game Server Protocol]]
 [[Category: Protocol]]

@@ Line 29: / Line 29: @@
 </pre>
-=== Also See ===
+=== See also ===
-[[Server to Directory Server Protocol]]
+[[Directory Game Server Protocol]]
 [[Category: Protocol]]

@@ Line 2: / Line 2: @@
 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>
@@ Line 28: / Line 28: @@
 packet repeats from offset 1 until end
 </pre>
 [[Category: Protocol]]

@@ 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.
-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>