On 8/30/07, Moshe Weitzman < weitzman@tejasa.com> wrote:

sean - thats basically what chx' lats patch proposed. caching was
skipped if a variable was present. a contrib module could manage
setting of that var. the patch was denied in favor of rollback.

On 8/30/07, Sean Robertson <seanr@ngpsoftware.com > wrote:
> > If we have a technology like node caching that is only used on 3 major
> > Drupal sites via patches, with each implementation custom or slightly
> > different, it will certainly not be any more stable for Drupal 7 than it
> > is now.  If we have hundreds or thousands of people who just have to
> > click a radio button or add an option to settings.php to turn on node
> > caching and label it as experimental, then we can begin to stabilize
> > this great performance boosting technology.  If it doesn't work with
> > your particular set of modules, fine, turn it off and no harm done.
> >
> > I believe that since nodes are the crux of the Drupal system, releasing
> > Drupal 6 without this technology is a real shame since there are so many
> > great performance options that will be available for Drupal 6.
>
> I agree with this.  How hard would it be to make it an option, just like
> the advanced cache option in Drupal 5 and warn users that it could cause
> issues in some circumstances.
>
>
>
> --
> Sean Robertson
> Web Developer
> NGP Software, Inc.
> seanr@ngpsoftware.com
> (202) 686-9330
> http://www.ngpsoftware.com
>