Re: A patch to keep cache directory out of webroot

My opinion: leave multisites the way it is now, where you have site 
specific folders in whatever 'xarsites' folder you configured it for. 
  No matter  what, you will somehow have to tell xaraya where the /var/ 
folder is for each multisite.  If a multisite is already using the 
config file in it's own /var/ folder, then it should be able to write 
cache to that folder's cache folder, etc.  If you have a single /var/ 
folder (and everything is like it is now with multisites) which has, for 
instance, /var/cache + /var/sites/site1/cache/ xaraya will be writing 
cache to /var/cache/ for the master and the multisites, until you tell 
the multisite installation where it's cache folder is.  You will have to 
enable xaraya to know this is a multisite and this is the 
/var/sites/site1/var/ folder where /cache/ + /uploads/ + /processes/ + 
etc. belong.

I think, if you are going to make the /var/ folder moveable, it will 
have to be configured during the initial install to tell xaraya where 
everything is.  If this is the case, I don't see why the multisites 
can't have their own 'sites' folder (even outside of root) for /var/. 
Unless multisites is changed so you can configure a folder for each 
install, instead of 'xarsites' containing all multisites /var/ folders, 
they will still be grouped together, so why not let the admin choose 
where that folder is? To me, it seems more secure to make folders 
moveable (not only to outside of the webroot), even though most people 
probably wont bother.  Peronally, I'd keep my multisites under the 
master site's /var/ directory, but some people may have certain 
situations where they need a multisite's /var/ folder else where, away 
from the master's /var/ folder.

Now, I realize that is just a tiny piece to a huge complex megastorm of 
opinionated discomfort and agrevation.  But, I think somewhere 
compromise is going to be required.  I'm not on the team, I'm just a 
luser, but normally I think breathing before, during, and after 
reading/reacting/responding to posts is probably a good idea sometimes :)

This is text, no emotion, no facial expression, no way to read between 
the lines, sometimes it's hard to know how someone meant to say 
something.  I think the patches newsgroup isn't such a good place for an 
extended thread such as this one.  Perhaps some private dev talk and 
brainstorming, then show us all what the options are and discuss it 
publicly.

Just my 1/100 Peso (darn budget cuts)

David.D