That's actually what we're planning on. See here:
http://cake.insertdesignhere.com/files/nyphp_presentation.pdf, slide
#38.
On Mar 23, 7:40 am, "thequietlab" <[EMAIL PROTECTED]> wrote:
> well..
> having cache as an object would be definitely more robust as one can
> overwrite the cake default be
I think this is what you are looking for.
http://rossoft.wordpress.com/2006/03/15/cache-objects-component/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to cake-
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 ? ;)
bt
On 3/23/07, thequietlab <[EMAIL PROTECTED]> wrote:
>
>
> maybe I confused something .. but I'm looking at 'cake/libs/
> cache.php' (v.1.2) - this one definitely interacts with database
Ignore that file, it is in never used by the core, and I doubt anyone is
using it anywhere else.
I plan to remo
maybe I confused something .. but I'm looking at 'cake/libs/
cache.php' (v.1.2) - this one definitely interacts with database
On 23 Mar, 00:27, "Grant Cox" <[EMAIL PROTECTED]> wrote:
> Where are you looking? Thecache() function in cake/basics.php writes
> to a file.
--~--~-~--~~--
Where are you looking? The cache() function in cake/basics.php writes
to a file.
--~--~-~--~~~---~--~~
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 u
I just noticed that cake's Cache class extends Model and is working on
a database to save and retrieve cached data. It's kind of strange
since caching should be used to NOT hit a database to save this
additional overhead.
I saw different ways of caching data using files and shared memory but
it's
You should keep all of your data storage functions on the model. So
either app_model if it needs to apply to all, or just the particular
model you want. Of course there will be cases where the data you want
to store is not particular to any model, and it makes more sense to
save/load from the co
Where would those first 2 functions go, ideally? In
app_controller.php? Still getting feet warm with cake. Thanks.
On Mar 2, 12:50 pm, "Mandy" <[EMAIL PROTECTED]> wrote:
> http://mandysingh.blogspot.com/2007/02/caching-with-cakephp.html
>
> On Mar 2, 3:32 pm, "phirschybar" <[EMAIL PROTECTED]> wro
http://php.net/serialize
On Mar 1, 10:05 pm, "phirschybar" <[EMAIL PROTECTED]> wrote:
> I see lots of info on caching views in the manual but I am wondering
> of I can cache an object as easily. Just a simple array of data so
> that I do not have to hit the DB on every page.
--~--~-~--~
http://mandysingh.blogspot.com/2007/02/caching-with-cakephp.html
On Mar 2, 3:32 pm, "phirschybar" <[EMAIL PROTECTED]> wrote:
> well gee. There you have it ;). Thanks.
>
> On Mar 1, 11:03 pm, "Grant Cox" <[EMAIL PROTECTED]> wrote:
>
>
>
> >http://bakery.cakephp.org/articles/view/249
>
> > phirschy
well gee. There you have it ;). Thanks.
On Mar 1, 11:03 pm, "Grant Cox" <[EMAIL PROTECTED]> wrote:
> http://bakery.cakephp.org/articles/view/249
>
> phirschybar wrote:
> > I see lots of info on caching views in the manual but I am wondering
> > of I can cache an object as easily. Just a simple ar
http://bakery.cakephp.org/articles/view/249
phirschybar wrote:
> I see lots of info on caching views in the manual but I am wondering
> of I can cache an object as easily. Just a simple array of data so
> that I do not have to hit the DB on every page.
--~--~-~--~~~-
I see lots of info on caching views in the manual but I am wondering
of I can cache an object as easily. Just a simple array of data so
that I do not have to hit the DB on every page.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to th
14 matches
Mail list logo
