Re: [need for advices] fastCaching

(Fabien) > > So I have written a class (called fastCache) less flexible and maybe > > less powerfull than PEAR/Cache. There is no container approach. The > > cache is stored in files. For the problem of require_once('PEAR.php'), I > > use the following idea : > > - in most cases, the class doesn't include anymore. > > - but if an error is detected, the class will include PEAR.php > > dynamically (with include_once and not require_once) and then will call > > PEAR::raiseError (Martin) > Including PEAR.php "per request" should be even possible with the > current PEAR Cache, no? And perhaps there are some possibilities to > even tune the container code? I have worked a lot with this Cache and I think that is possible to improve perfs but... for a big jump, you have to forget the container idea and focus yourself on file container. For including PEAR.php "per request" in the current Cache, maybe but there is a lot of changes to do (emulate destructor, don't use Cache_Error...). If I tune PEAR/Cache for perfs, I will break its spirit I think. That's why I wrote a new class with a different conception. > BTW: Please be aware that PEAR Cache does not perform well for *real* > high-traffic sites. In such a case one should consider using Zend > Cache. Zend Cache isn't free... :-(( > My opinion towards your new package: Why do you want to reinvent the > wheel before having tried to improve the existing solutions? Anyways, > I will not keep you away from contributing, if others agree on your > plan. I hate reinvent the wheel :-)) But if you want some very good perfs, you have to write a new class because the spirit is very different. So I maintain my plan but I will respect your (or other) decision if you maintain it too after this new post :-)) Fabien