Re: A patch to keep cache directory out of webroot

"Jason Judge" <[email protected]> wrote in message 
news:[email protected]...
>
>
> xarCoreGetVarDirPath('mymodule') - e.g. /home/http/var/xar
> xarCoreGetVarDirPath('mymodule', 'public', 'virtual') - e.g. /documents
> xarCoreGetVarDirPath('mymodule', 'public', 'real') - e.g. 
> ~htroot/documents

I've posted elsewhere here - but if i see this then we need to really define 
what the /var (or whateve you want to call the directory) should include. 
What should it be used for.

I believe we are moving away from the original intent of the vardirpath. I'd 
like to keep it simple, with the sole purpose of directing to where the 
config options are to install Xaraya and minimal boot requirements for the 
one, or any other site running off the code base installation.

Keeping in mind:
* Configurable 'site specific' configurations should be able to have their 
own equivalend of a var directory with all the config options there
* Data should be kept elsewhere on a per site basis and probably would be a 
writeable and web accessible dir
* Modules should handle their own *optional* configurations for paths 
outside the webroot. They will need only, the basic structure that we settle 
on (when we do) to work with so they can have optional paths in, out or both 
;).

Sometimes too, the decisions lie with server and site admins who need to 
take some responsibility for their sites and where they store data - and 
sometimes the operator has no choice at all.

Jo

> ?
>
> -- JJ
>
>