-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Note that compressing anything that has already been compressed, such
as most image, audio, or video formats, is pointless.
Ian.
On 19 May 2006, at 09:56, Matthew Toseland wrote:
Most of the time I expect the node to decide what goes into a
container.
How can it decide this? I propose the following rules:
- Anything which is over 3 blocks compressed (10 blocks uncompressed?)
should not go in a manifest.
- Anything much larger than the average probably shouldn't go in a
manifest.
- Content of the same type should go in the same container, in
order to
optimize compression.
- Small uncompressible content should go into a container, but not the
same manifest as highly compressible content e.g. HTML.
Hence, the Hardware Book might have two tar.bz2's, one containing all
the HTML, and the other containing everything else. The base redirect
block would contain the top level metadata for both manifests.
Is it useful to split a site up into multiple containers?
Certainly we should let the client provide hints as to how to slice up
the site, but it may be useful to split it up without reference to the
directory structure of the site... Maybe on ClientPutComplexDir,
an optional ContainerName for each file?
--
Matthew J Toseland - [EMAIL PROTECTED]
Freenet Project Official Codemonkey - http://freenetproject.org/
ICTHUS - Nothing is impossible. Our Boss says so.
_______________________________________________
Devl mailing list
[email protected]
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)
iD8DBQFEbfvtQtgxRWSmsqwRAjeIAJ4gB3hlEf9OmnIiF0SyXPuMNOAUdACfYH2v
83gkVQkGG+zURDAjUO+KLlc=
=vFU+
-----END PGP SIGNATURE-----
_______________________________________________
Devl mailing list
[email protected]
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
