On Tue, Oct 28, 2003 at 12:53:24PM +0100, Some Guy wrote: > --- Toad <[EMAIL PROTECTED]> wrote: > > On Mon, Oct 27, 2003 at 01:54:16PM +0100, Some Guy wrote: > > > --- Nick Tarleton <[EMAIL PROTECTED]> wrote: > > > > I have heard a lot about Freenet's emergent behavior and would like to > > > > understand just what mechanisms in the code make this happen. > > > > > > I'll do my best to answer these guys for you. > > > > > > > > Key size is small; you probably mean the size of the data asssociated with the > > > key. A > > requester > > > usually has no clue how large the data is until he get's it back. > > > > > > Size is corrected for when we calculate how long it takes a node to reply. > > > > Wrong. The node, and everyone else, know exactly how large the key is, > > from the URI. The node uses this information in routing (NGRouting > > anyway). > > Sorry, I was wrong in the case of CSKs. My bad!!! I was just thinking about KSKs > and SSKs, > where you can't know the size.
You can. They may be out a little, but since there's a limit of 32kB, it doesn't matter much. The thing is, the metadata in the content may redirect to another, larger key. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
signature.asc
Description: Digital signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
