dstruve wrote
chavous so what was your conclusion on this issue?
That caching doesn't work on anything but the simplest of modules... txt/html modules come to mind... and even those have been known to be kludgy...
Links modules seem to be ok as well... maybe document modules - not sure on those...
All other modules should be left alone, because the caching system just can't handle anything else... if the module accepts ANY parameters on its face (like, for example, it allows you to change DATES like a calendar or search forward/next, etc) the caching won't do any good ANYWAY, and in MOST/MANY cases, will crash like a six-year-old driving a bumper car...
and most SHOULD have their own internal caching or optimization mechanism if they are, for example, an RSS feed or otherwise present a fairly static front-end. Most probably don't YET - but I know, at least on the calendar module, "they" were talking about doing SOMETHING to make it more efficient. I personally haven't had any major issues with it, but then again, my biggest portal has 70 registered users, and likely won't grow beyond 1000 - and thats if we get every single person in the state who falls in to our group registered... :) Even then - it isn't an ACTIVE group - it is an 'occasionally check the site' type group...
I had actually stopped monitoring the thread when I figured that out a while ago... I saw y'all jumped on it and ran with it... :)
I was looking through my old posts and saw you addressed me directly, so I figured I'd respond.