Diff: [root] @ 0698d2499fe | faq | css

more meta docs

File: hellnet/protocols/http/meta [Diff]

-- a/hellnet/protocols/http/meta++ b/hellnet/protocols/http/meta
@@ -16,8 +16,6 @@

This resource provides metatrees, its dates and signatures

When updating, client should first check the date; if it's bigger than his current metatree, then client downloads the tree and signature, optionally decrypts both using supplied encryption key and checks if server's announced date, key and name match ones in metatree itself and the signature validity. If these are ok, then it replaces its own metatree with downloaded one.

h4. Response

Metatree, its date and signature. Example:

File created: hellnet/tech/URIs/chunk [Diff]

-- /dev/null++ b/hellnet/tech/URIs/chunk
@@ -1 +1,17 @@
h1. Chunk hell:// URIs

h2. Regex

^hell://chunk/([0-9a-f]{64})$

$1: chunk hash

h2. Optional parameters

name: Any string, contents' filename
key: hex number, symmetric encryption key

h2. How it works

Searches for chunk with hash=$1, then downloads it. Name is received from "name" parameter, otherwise $1(.key) may be used.

File created: hellnet/tech/URIs/file [Diff]

-- /dev/null++ b/hellnet/tech/URIs/file
@@ -1 +1,17 @@
h1. File hell:// URIs

h2. Regex

^hell://file/([0-9a-f]{64})$

$1: chunk hash

h2. Optional parameters

name: Any string, contents' filename
key: hex number, symmetric encryption key

h2. How it works

Searches for chunk with hash=$1, then unrolls it as [[../recursive-filelinks|recursive filelink]] and downloads the file. Name is received from "name" parameter, otherwise $1(.key) may be taken.

File created: hellnet/tech/URIs/meta [Diff]

-- /dev/null++ b/hellnet/tech/URIs/meta
@@ -1 +1,23 @@
h1. Meta hell:// URIs

h2. Regex

^hell://meta/([0-9a-f]{64})/([^/]+)/(.*)$

$1: public key hash
$2: meta name

h2. Optional parameters

name: Any string, contents' filename
key: hex number, symmetric encryption key

h2. How it works

When updating, client should first check the date; if it's bigger than his current metatree, then client downloads the tree and signature, optionally decrypts both using supplied encryption key and checks if server's announced date, key and name match ones in metatree itself and the signature validity. If these are ok, then it replaces its own metatree with downloaded one.

h2. See also

* [[../../protocols/http/meta|meta resource]]
* [[../metatrees]]

By Voker57 on 2009-11-19 19:10:09 +0000