On Monday 23 June 2003 01:09 pm, Toad wrote: > The answer is to implement containers. I have nothing against > containers. I just haven't gotten around to it yet due to having more > important things to do. But there are many other people who could > implement it.
I hate to open another can of worms (I seemed to have developed a habit of that lately.) But while we're on the subject of containers ... Users might be tempted to say: "Golly gee, it looks so nice when all the images are loaded with the page, I'll just throw all the HTML and images for my DBR site into one big zipfile ..." One way to deter this, (although it might have to be coupled with severe floggings), would be for the Meta key to put the CHKs into groups. Like for example if the main page index.html linked to image.png that could be the next entry with a bit added to indicate that if you end up fetching index.html you might as well also immediately request image.png because you will in a second anyways. Now this could be abused. IE: If some site decided that 'OK, how that you have loaded index.html, you probably also want this 600MB movie!'. However if a site was that bad others would not link to it. (Plus it probably shouldn't request anything beyond the metadata for a splitfile until it determines the user really wants it.) This would speed the loading of images, and hopefully would be implemented in the insertion utility so newbes would not end up messing with it. This would also help eliminate the problem described at: http://127.0.0.1:8888/[EMAIL PROTECTED]/SSKvsCHK/2// _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
