[development] CCK per field CRUD settings, caching complexity

Bèr Kessels ber at webschuur.com
Mon May 29 10:15:18 UTC 2006

Op zaterdag 27 mei 2006 21:42, schreef Adrian Rossouw:
> i think the object should always be completely cached (ie: one cache  
> per node)
> but the node load access mechanism should trim what you don't have  
> the right to see.

Sounds like a plan. But this defeats the whole point of caching..... But I 
will certainly investigate this route. 

Another concept Ive been looking at is caching per chunk. So not caching a 
complete node, but only caching the parts of the node and then compile them 
on load. There could be a possibility to cache that compiled version too.


More information about the development mailing list