Smarty

[jtm]

It seems that when using custom cache handler function the call to is_cached executes the custom handler with 'read' action. This makes the handler to fetch the entire cache page from somewhere.

Because is_cache only need to know if the page is in cache or not, the custom cache handler function fetchs the cache data for nothing:

suggestion:

Add 'is_cache' action into the custom cache handler so that the developper who creates his own cache handler function can optimize this (for example, the function can just check if (file_exists(...)) without actually opening and reading the file.)

- jtm

edit: typos

[messju]

it is intended behaviour that is_cached() reads the file. this is regardless of a user defined cache_handler_func() or the built-in one. this avoids a race-condition that may occur between the is_cached() and the fetch() call. if is_cached() was called before then fetch() simply returns the page that was gathered with is_cached() before.