File diff: [root]/hellnet/protocols/queries @ 7b26924aef0 | src | log | faq | css

diff --git a/hellnet/protocols/queries b/hellnet/protocols/queries
index 49dc877..cdfbcb5 100644
-- a/hellnet/protocols/queries
++ b/hellnet/protocols/queries
@@ -1,6 +1,6 @@
h1. DEPRECATED

This page contains deprecated information. This has been replaced with [[http|HTTP interfaces]]. "HTTP interfaces":http.

h1. Hellnet queries

@@ -8,15 +8,15 @@ Warning: This document is WIP(Work In Progress) and incomplete. No implementatio

h2. Basics

Query is valid Hellnet [[transfer|transfer module]] "transfer module":transfer that has three mandatory fields:
* 'hops' -- number of peers that this query has gone through.
Should start with random value from 0 to 5 (or more) for anonimity purposes and every peer must add 1 to its value. After certain amount of hops chances of dropping query should increase with every peer.
* 'type' -- query type.
The one currently defined type is 'hash', which queries for data with hash specified in 'args'.
* 'args' -- query arguments.
A string that contains query arguments (such as data digest for 'hash').
* 'id' -- unique ID of query, is [[../crypto/hash|digest]] "digest":../crypto/hash of string 'type:args:origin'.
* 'origin' -- key ID of query origin.
* 'signature' -- cryptographic (GnuPG?) [[/hellnet/crypto/asymmetric|signature]] "signature":/wiki/hellnet/crypto/asymmetric of 'id', made with secret key from 'origin'.

Queries are created by node 1, being passed over to other nodes. One node should [[responses|respond]] "respond":responses to query if it has needed information and not overloaded, thus stopping passing the query, or pass query along otherwise.

By Voker57 on 2012-01-29 17:17:28 +0400 Powered by bitcheese wiki engine