well.. having cache as an object would be definitely more robust as one can overwrite the cake default behaviour with he's own cache handlers (eaccelerator,memcache etc..) and keep everything clean & clear.
So maybe think about moving real cache functionality there instead of removing it ? ;) btw. it was funny to see database query's inside Cache class ;) On 23 Mar, 12:23, "Larry E. Masters aka PhpNut" <[EMAIL PROTECTED]> wrote: > On 3/23/07, thequietlab <[EMAIL PROTECTED]> wrote: > Ignore that file, it is in never used by the core, and I doubt anyone is > using it anywhere else. > I plan to remove before 1.2 is stable unless someone can convince me that it > should be saved, and I am not that easy to convince. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
