[TYPO3-50-general] server vs web root / temp vs cache
Martin.Kutschker at n0spam-blackbox.net
Mon Oct 16 17:11:09 CEST 2006
Robert Lemke schrieb:
> Hi Martin,
> Martin Kutschker write:
>> I'd like to see a changed directory layout that distincts between
>> server side application code (PHP) and data on the one hand and
>> clients side code (JS) and web resources (eg images) on the other hand.
>> Further I want to see this distinction in temp./cache directories. A
>> true temp. directory must no be exposed to the world OTOH many things
>> that are in typo3temp are really cache data. Some of this cached data
>> are again for internal purposes and others are for the web.
> I agree. On Monday I have started to do a little brainstorming for a
> future directory structure. As I imagine that *all* content is stored in
> the content repository, we obviously need a kind of cache for the
> frontend which holds all the files - be it assets for an HTML template,
> Currently, I think about a directory called "filecache/" in the root
> webspace dir. Something like this:
I think you mean something different with cache than I do. With cache I
mean a temporary storage for the application (usually used to store results
of an expensive operation), eg browser page cache or db query cache.
So using my term I do not store templates in a cache. But I do store
rendered pages in a cache.
More information about the TYPO3-project-5_0-general