On Monday 23 June 2003 12:06 pm, Tom Kaitchuck wrote: > No matter how widely distributed it is, it > is just not worth making a network request for 100+ images that are less > that 100 bytes. But this is only to see them all, on the PROMS site. Not everyone has to do that, and they won't have to do it that often.
> What I'm proposing is NOT to load all the images into fproxy like the > existing images (where they would take up memory and be version dependent), > But rather if fproxy did a simple string replace on > "http://127.0.0.1:888/images/"; and substituted > "file://$FREENETDIR/images/". Then the rest would be for the browser to > sort out. This is far simpler than substituted HSK A for HSK B and would > have virtually no overhead in fproxy. This would still make the distribution big. Not overly big, though. However, it suffers from the common mistake of thinking that people ALWAYS browse freenet from the same machine as their node! It also messes up people under Un*x who are browsing as a different user than they run their node. Sorry to shout, but it's NOT GONNA WORK this way. It would work to have them in the one-time download with things like freenet-ext.jar, but it's still unnecessary bloat when they can just be in Freenet and accessed via CHKs. The less popular ones will fall out, the more popular ones will stay in, and if there are problems anybody can reinsert them. (Note: The differing metadata bug rears its ugly head here - if the initial insert is with, say, fproxy, then all future inserts must be with fproxy. This should be stated on the PROMS site, but we _really_ need a standard.) -- "I love deadlines. I love the whooshing sound they make as they go by." - Douglas Adams Nick Tarleton - [EMAIL PROTECTED] - PGP key available _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
