That's because it would be abusing the system. The _right_ way to do it would be to store the main part of the site (the 100K you're talking about) in one .jar file, the archive section in a group of .jar files (e.g. one for each month) and whatever other big files you have in there as external CHK's. This would have all the benefits I'm talking about and _none_ of the disadvantages you're talking about...
Yves Lempereur
fish wrote:
Consider my freesite for a moment:
jaymz@chuckie:~$ du fishland -sh
6.7M fishland
you probably want (assuming you wanted to read fishland, which you don't,
but lets pretend) maybe 100k of that at any given time, unless you're
actully reading through the archives.
to summerise, no :-p
- fish
On Wed, 20 Nov 2002, Tyler Riddle wrote:
> This was posted to [EMAIL PROTECTED] but I did
> not see any word of here or any activity regarding it
> on the tech list so I'm posting it here. This is
> something I have been advocating for a while (not
> entirely in this manor, but the functionality is the
> same) and I also posted to tech@ some time ago and got
> ignored as well. This would be a great feature but I
> see a huge potential for abuse as well. I think it
> would be worth it to discuss how to pull this
> particular feature off if it is at all possible with
> out bringing the network to it's knees.
>
> Tyler
- Re: [Tech] Re: Re: tying freesites together with jars Yves Lempereur
