Reply to For a Better Freenet ed 4: SSK at GOtXngpWwrbKaJWeaY1CbFz~sooPAgM,jXq8gyZ6fmiug87rSGJjuA/betterNet/4// - Searching: Cyberdo is implementing a web page search. - Containers: The GPL3 will be compatible with the ASL2. We can therefore use ASL2 code i.e. Commons Compress (which would give us tar.bz2 support) without too much worry re licensing. This will go in AFTER the alpha comes out. (The alpha won't have support for inserting containers). The node will indeed handle bundling, inserting a PUTDIR as separate files, a ZIP, a tar.bz2, or a combination of the above, depending on its capabilities. - Collections: It may be useful to have some sort of prefetch, but not yet. - Automated editions: The current proposal is to implement USKs. These will be initially based on automatic edition checking, but can be updated in future versions of the node without the client having to worry about it. We can then use DBRs, hierarchical DBRs, TUKs etc. - IP load: the UDP bandwidth limiter in 0.7.0 should work very well (for upstream limiting) because we can precisely control what packets we send. We may include an average bandwidth limiter too. Some bugs have been reported... We will probably not include a downstream limiter as this is very difficult - at least not in the alpha. - UDP: freenet 0.7 will use UDP, and already does use UDP. - FEC: We cannot use LDPC codes as it is likely that ALL LDPC code implementations are covered by the numerous patents on this technique. Therefore we will stick with Vandermonde Reed-Solomon codes as implemented by the onion codes. - Java compat: Thanks to nextgens' efforts, freenet 0.7 now runs on GCJ. Unfortunately there are some performance issues making it more or less unusable at present. - SHA256: We use SHA-256 everywhere in Freenet 0.7. Including for routing keys, which are now 32 bytes (and are hashed with SHA-256 before routing to make key-based DoS harder). - Darknet: 0.7 is at the moment a darknet. Opennet support will be added later, after the alpha. - Monolithic datastores: 0.7 at present uses a monolithic datastore, backed by Berkeley DB Java Edition. - Prefetching channels: Would tie in reasonably well with USKs. Something to consider after the alpha. - Priorities: We will not include request priorities in 0.7. Local, queued requests can indeed have a range of priorities. But once they leave the node they are homogenous. Publish/subscribe etc will probably involve subscribing to a stream of SSKs via passive requests. -- 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/20060307/a7258be9/attachment.pgp>
