On Fri, Apr 27, 2001 at 01:22:56PM -0500, Brandon wrote:
>
> > No, it really wouldn't. The "perceived performance surfing Freenet
> > websites" is caused by the latency traversing the network to
> > search for the data. Compression of the data wouldn't help with that at
> > all.
>
> BTW, I figured out how to eliminate this problem. The solution is to have
> a pre-fetching caching web proxy between your browser and FProxy. That way
> whenever you go to a site all of the links will be already cached in your
> node. This will also help with site propagation because sites will
> propagate altogether rather than having the index page receive a lot more
> hits, resulting in often broken links.
>
> Of course there are some necessary tweaks. For instance you probably don't
> want to prefetch links to movies.
How do you know they are movies? You'd just have to go on filenames, since
aborting a transfer on freenet is pretty meaningless.
>
> I've found, unfortunately, that there are no working pre-fetch web proxies
> currenly in existing (some old ones from 96 that don't work, though). So
> someone should really add a parameter to FProxy to turn on internal
> pre-fetching. Alas, I don't have time to write this right now.
wcol is one possibility. Search for it on freshmeat. From 99, not 96. This has
been suggested before :)
--
Anarchists who refuse to learn the use of computer networks deserve to
live in slavery
-- with apologies to Leon Trotsky
_______________________________________________
Devl mailing list
Devl at freenetproject.org
