On Sun, Sep 01, 2002 at 06:21:51AM -0700, [EMAIL PROTECTED] wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> As everybody seems keen on beefing up fproxy all of a sudden, here's a
> few suggestions for some little changes you all might like to consider,
> 
> 1) Death to the evil browser cache.
> 
> For all the security Freenet provides, browsing freesites still leaves
> a trail of cached pages behind. I'm sure there must be some HTTP
> directive to instruct the browser to not cache pages, but unfortunately
> I can't think of it right now. Also, if this feature can be added,
> please make it optional, as some strange people may actually like the
> caching behaviour kept as it is.
Hmmmmm.
> 
> 2) SSL Freesite browsing.
> 
> I seem to dimly recall this being discussed a long time ago now, and I
> forget why it never actually came to anything. Although I do notice
> some old SSL interface code still lurking around the Freenet source
> tree, seemingly doing nothing.
> 
> As there seem to be quite a few people who like to leave their nodes
> running 24/7, and access them from remote locations during the day,
> leaving fproxy without a secure socket option seems like a serious
> ommision IMHO.
> 
> Additionally, SSL browsing does have the extra bonus feature that
> most 'good' browsers will not cache SSL documents by default, and are
> careful about cleaning up any other little temp files that might be
> sitting around. So this ties in with the previous caching issue quite
> nicely I think.
> 
> 3) How to magically make freesites load faster ...
> 
Well, turning off caching is going to make freesites load SLOWER.
> OK, so maybe not physically faster, but I notice fproxy doesn't seem to
> stream keys to the browser as they are retrieved from the network. I'm
> sure I remember fproxy 0.3 supporting this though.
Hmm, correct behaviour is to stream in verified chunks of 4kB.
> 
> Most modern browsers support streaming the display of web pages, so
> if 'some' HTML, or a bit of an image can be made to appear just that
> little bit faster (ok, actually a lot faster in many cases I suspect),
> then I say that's got to be worth looking into.
> 
> At the moment, many freesites *appear* to fetch very slowly, when this
> need not be the case.
> 
> Anyway, I'd be interested to hear what people think of my suggestions.
> 
> Thanks.
> 
> CofE.
> 
> -----BEGIN PGP SIGNATURE-----
> Version: Hush 2.1
> Note: This signature can be verified at https://www.hushtools.com
> 
> wl4EARECAB4FAj1yFIQXHGNvZmUtbWFpbEBodXNobWFpbC5jb20ACgkQFbDVjdIJmIW8
> /ACfYIAAetnC/7pkZJRjkFDeZIgnQysAoJ4+cLwOHR9Cp10zyYJQ0Od2JiOI
> =lwbF
> -----END PGP SIGNATURE-----
> 
> 
> 
> 
> Get your free encrypted email at https://www.hushmail.com
> 
> _______________________________________________
> devl mailing list
> [EMAIL PROTECTED]
> http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
> 

Attachment: msg03733/pgp00000.pgp
Description: PGP signature

Reply via email to