[development] node caching

Moshe Weitzman weitzman at tejasa.com
Wed Aug 29 16:10:26 UTC 2007

1. your data must now be dynamic after load. you make changes in
nodeapi('view') operation for example. if this causes pain, please
give a use case that can't be reworked to play nice with a node laod
2. see #1
3. the node access api is not involved in node caching. it just is
some data that is keyed by nid. it is not loaded into $node object.

On 8/29/07, Robert Douglass <rob at robshouse.net> wrote:
> Sorry for jumping into this late in the game, but I was only aware of
> node caching after it went in.
> Just for my edification, please explain how, in Drupal 6, how one
> handles these three situations:
> 1. dynamic data
> 2. role based differences between loaded nodes
> 3. node_access based differences between nodes.
> Please understand, I'm a great fan of caching and would love to see node
> caching; I just need to understand how module programmers are supposed
> to handle these cases, since in D5 they could do all of this in nodeapi
> without cause for concern.
> Thanks
> Robert

More information about the development mailing list