moparisthebest/rswiki-book
1
0
Fork 0
mirror of https://github.com/moparisthebest/rswiki-book synced 2024-12-26 01:09:15 -05:00
Code Issues Releases Wiki Activity

Create MediaWiki page 'JAGGRAB Protocol'

Browse Source
This commit is contained in:
Jmood 2012-08-28 02:13:03 +00:00 committed by moparisthebest
parent ccf1fa7551
commit a198ce0628
3 changed files with 44 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
Categories.mediawiki
View File

@ -1,5 +1,6 @@
<!-- DO NOT EDIT THIS FILE, CODE AUTOMATICALLY GENERATED BY category.sh -->
The following categories contain pages or media.
* [[Category Cache]] (1 members)
* [[Category Data Type]] (3 members)
* [[Category Packet]] (91 members)
* [[Category Packet 194]] (4 members)

6
Category-Cache.mediawiki
View File

@ -2,4 +2,8 @@
== '''JAGGRAB Protocol''' ==
== '''Ondemand Protocol''' ==
== '''Ondemand Protocol''' ==
<!-- DO NOT EDIT BELOW THIS LINE, OR CHANGE THIS COMMENT, CODE AUTOMATICALLY GENERATED BY category.sh -->
== '''Pages in category "Cache"''' ==
The following 1 pages are in this category.
* [[JAGGRAB Protocol]]

38
JAGGRAB-Protocol.mediawiki Normal file
View File

@ -0,0 +1,38 @@
[[Category Cache]]
== Introduction ==
The JAGGRAB protocol is used to 'grab' cache files from the file server and download them.
It is a text-based protocol, similar to HTTP, and the client will fall back to HTTP if JAGGRAB is unavailable. This generally happens in unsigned mode and helps users who are behind firewalls.
== Request format ==
A request is simply the text JAGGRAB, a space, the path to the file and a newline character. Therefore, it is very similar to a HTTP/0.9 GET request.
JAGGRAB /path/to/file
=== New engine ===
In (perhaps all) new engine clients, the client prefixes the JAGGRAB request line with a single byte (value 17).
== Response format ==
The response is simply the raw file data. Once the response is sent, the connection is closed.
== Files ==
There are a number of files which map to files in the cache.
* '''/crc''' - the CRC table
* '''/title''' - cache 0, file 1
* '''/config''' - cache 0, file 2
* '''/interface''' - cache 0, file 3
* '''/media''' - cache 0, file 4
* '''/versionlist''' - cache 0, file 5
* '''/textures''' - cache 0, file 6
* '''/wordenc''' - cache 0, file 7
* '''/sounds''' - cache 0, file 8
NOTE: the client will usually postfix these with random numbers, so when checking for the file only the start of the string should be examined: not the whole one.<BR>
NOTE: The crc is postfixed with the client revision