Difference between revisions of "JAGGRAB Protocol"

From RuneWiki
Jump to navigationJump to search
(New page: The JAGGRAB protocol is used to 'grab' cache files from the file server and download them. It is a text protocol, similar to HTTP, and the client will fall back to HTTP if JAGGRAB is unav...)
 
Line 12: Line 12:
  
 
The response is simply the raw file data. Once the response is sent, the connection is closed.
 
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

Revision as of 08:39, 12 August 2009

The JAGGRAB protocol is used to 'grab' cache files from the file server and download them.

It is a text protocol, similar to HTTP, and the client will fall back to HTTP if JAGGRAB is unavailable. This generally happens in unsigned mode.

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

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