I will implement SSKs for 0.7.0 soon. One remaining issue is how big should SSKs be? 32kB PRO: Fit in datastore like any other key. CON: Not good for streams (well some kinds of streams). PRO: Files often fit inside the SSK, so save a redirect... CON: ... But this means we lose an opportunity for coalescing CHKs. CON: Metadata carried by SSKs will often be much smaller than 32kB.
1kB PRO: Good for streams (which can then just be a sequence of passive requests for SSKs). PRO: Closer to typical metadata size. CON: But maybe a bit too small. CON: Doesn't fit in the datastore as a normal key. PRO: So we can store many more of them in a separate store. PRO: And we don't have to worry about the fact that SSKs don't really fit anyway, because their header fields are huge. -- Matthew J Toseland - toad at amphibian.dyndns.org Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20051118/18e76e56/attachment.pgp>
