<?xml version="1.0"?>
<?xml-stylesheet
href="http://www.w3.org/2000/08/w3c-synd/style.css" type="text/css"
?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel rdf:about="http://pear.php.net/bugs/search.php">
    <title>PEAR Bug Search Results</title>
    <link>http://pear.php.net/bugs/search.php?cmd=display&amp;package_name%5B0%5D=Cache_Lite</link>
    <description>Search Results</description>
    <dc:language>en-us</dc:language>
    <dc:creator>pear-webmaster@lists.php.net</dc:creator>
    <dc:publisher>pear-webmaster@lists.php.net</dc:publisher>
    <admin:generatorAgent rdf:resource="http://pear.php.net/bugs"/>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>
    <items>
     <rdf:Seq>
      <rdf:li rdf:resource="http://pear.php.net/bug/19712" />
      <rdf:li rdf:resource="http://pear.php.net/bug/17774" />
      <rdf:li rdf:resource="http://pear.php.net/bug/17269" />
      <rdf:li rdf:resource="http://pear.php.net/bug/13297" />
      <rdf:li rdf:resource="http://pear.php.net/bug/12179" />
      <rdf:li rdf:resource="http://pear.php.net/bug/10502" />

     </rdf:Seq>
    </items>
  </channel>

  <image rdf:about="http://pear.php.net/gifs/pearsmall.gif">
    <title>PEAR Bugs</title>
    <url>http://pear.php.net/gifs/pearsmall.gif</url>
    <link>http://pear.php.net/bugs</link>
  </image>

    <item rdf:about="http://pear.php.net/bug/19712">
      <title>Cache_Lite: Feature/Change Request 19712 [Open] clearstatcache use on write only</title>
      <link>http://pear.php.net/bugs/19712</link>
      <content:encoded><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by gamesh
2012-11-20T12:37:55+00:00
PHP: 5.2.17 OS: Windows Server 2008 R2 Package Version: 1.7.15

Description:
------------
I would like to propose to use clearstatcache() only on writing to cache, as it should occur relatively rarely compared to reads form cache. And since now you flush stat cache on every read, PHP can't use real path stat cache for file_exists and other file operations related to paths. It decreases performance.

and the only time anything changes is when you write to cache - create new files, or clean cache so maybe it would be wise to clear it only on write and clean.</pre>]]></content:encoded>
      <description><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by gamesh
2012-11-20T12:37:55+00:00
PHP: 5.2.17 OS: Windows Server 2008 R2 Package Version: 1.7.15

Description:
------------
I would like to propose to use clearstatcache() only on writing to cache, as it should occur relatively rarely compared to reads form cache. And since now you flush stat cache on every read, PHP can't use real path stat cache for file_exists and other file operations related to paths. It decreases performance.

and the only time anything changes is when you write to cache - create new files, or clean cache so maybe it would be wise to clear it only on write and clean.</pre>]]></description>
      <dc:date>2012-11-20T12:37:55+00:00</dc:date>
      <dc:creator>justinasu &amp;#x61;&amp;#116; gmail &amp;#x64;&amp;#111;&amp;#x74; com</dc:creator>
      <dc:subject>Cache_Lite Feature/Change Request</dc:subject>
    </item>
    <item rdf:about="http://pear.php.net/bug/17774">
      <title>Cache_Lite: Feature/Change Request 17774 [Open] Patch: Avoid deprecated function calls</title>
      <link>http://pear.php.net/bugs/17774</link>
      <content:encoded><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by olleolleolle
2010-08-21T05:58:48+00:00
PHP: 5.3.1 OS:  Package Version: SVN

Description:
------------
WARNING: Function 'set_magic_quotes_runtime' is deprecated, 
its use is no longer recommended in file:
./Cache_Lite/Lite.php line 716
                             line 728
                             line 775
                             line 779</pre>]]></content:encoded>
      <description><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by olleolleolle
2010-08-21T05:58:48+00:00
PHP: 5.3.1 OS:  Package Version: SVN

Description:
------------
WARNING: Function 'set_magic_quotes_runtime' is deprecated, 
its use is no longer recommended in file:
./Cache_Lite/Lite.php line 716
                             line 728
                             line 775
                             line 779</pre>]]></description>
      <dc:date>2014-05-10T14:49:17+00:00</dc:date>
      <dc:creator>olle &amp;#x64;&amp;#111;&amp;#x74; jonsson &amp;#x61;&amp;#116; gmail &amp;#x64;&amp;#111;&amp;#x74; com</dc:creator>
      <dc:subject>Cache_Lite Feature/Change Request</dc:subject>
    </item>
    <item rdf:about="http://pear.php.net/bug/17269">
      <title>Cache_Lite: Feature/Change Request 17269 [Open] Extend Cache_Lite::lastModified() take a cache_id to return the age of an entry</title>
      <link>http://pear.php.net/bugs/17269</link>
      <content:encoded><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by l8gravely
2010-03-26T00:25:10+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
Hi,

I'd like to suggest that the Cache_Lite::lastModified() take a new arguement, which is the id of a cached object.  The return value would be the same as currently defined, though if the id did not exist, it should return -1, or some other error code.

This would allow me to pre-populate my web site with data which takes a long time to generate, and yet easily query the cache to see if I need to re-generate the output.

Another thought would be to extend some of the other existing methods to take a datestring which they check the cache file age against.  If the cache is older than the date string, return false (and clear that entry) otherwise just return the cached entry.

This could be:

  Cache_Lite_Output::start(  string $id , string $group = 'default' , boolean $doNotTestCacheValidity  = false, int older = '0')

where it checks if the age of the cached file is less than 'older' and returns False if true.</pre>]]></content:encoded>
      <description><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by l8gravely
2010-03-26T00:25:10+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
Hi,

I'd like to suggest that the Cache_Lite::lastModified() take a new arguement, which is the id of a cached object.  The return value would be the same as currently defined, though if the id did not exist, it should return -1, or some other error code.

This would allow me to pre-populate my web site with data which takes a long time to generate, and yet easily query the cache to see if I need to re-generate the output.

Another thought would be to extend some of the other existing methods to take a datestring which they check the cache file age against.  If the cache is older than the date string, return false (and clear that entry) otherwise just return the cached entry.

This could be:

  Cache_Lite_Output::start(  string $id , string $group = 'default' , boolean $doNotTestCacheValidity  = false, int older = '0')

where it checks if the age of the cached file is less than 'older' and returns False if true.</pre>]]></description>
      <dc:date>2010-06-09T14:39:50+00:00</dc:date>
      <dc:creator>john &amp;#x61;&amp;#116; stoffel &amp;#x64;&amp;#111;&amp;#x74; org</dc:creator>
      <dc:subject>Cache_Lite Feature/Change Request</dc:subject>
    </item>
    <item rdf:about="http://pear.php.net/bug/13297">
      <title>Cache_Lite: Feature/Change Request 13297 [Open] Support for per item lifetime</title>
      <link>http://pear.php.net/bugs/13297</link>
      <content:encoded><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by brunobg
2008-03-03T19:39:40+00:00
PHP: 5.2.2 OS: Linux Package Version: 1.7.2

Description:
------------
Cache_Lite supports changing the lifetime of an entry only globally, not per item. This patch provides an extension that allows the lifetime to be set per cache item.

Test script:
---------------
Provided in an attached file (.phpt)

Expected result:
----------------
Provided in an attached file (.phpt)

Actual result:
--------------
Not a bug.</pre>]]></content:encoded>
      <description><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by brunobg
2008-03-03T19:39:40+00:00
PHP: 5.2.2 OS: Linux Package Version: 1.7.2

Description:
------------
Cache_Lite supports changing the lifetime of an entry only globally, not per item. This patch provides an extension that allows the lifetime to be set per cache item.

Test script:
---------------
Provided in an attached file (.phpt)

Expected result:
----------------
Provided in an attached file (.phpt)

Actual result:
--------------
Not a bug.</pre>]]></description>
      <dc:date>2008-03-03T19:39:40+00:00</dc:date>
      <dc:creator>brunobg &amp;#x61;&amp;#116; users &amp;#x64;&amp;#111;&amp;#x74; sf &amp;#x64;&amp;#111;&amp;#x74; net</dc:creator>
      <dc:subject>Cache_Lite Feature/Change Request</dc:subject>
    </item>
    <item rdf:about="http://pear.php.net/bug/12179">
      <title>Cache_Lite: Feature/Change Request 12179 [Open] File.php: Allow timestamp in constructor in place of masterFile</title>
      <link>http://pear.php.net/bugs/12179</link>
      <content:encoded><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by mrclay
2007-10-03T14:54:38+00:00
PHP: Irrelevant OS:  Package Version: 1.7.2

Description:
------------
Cache_Lite_File is convenient when your cache validity depends on a single file, but it can't help you if you want validity to depend on a set of files, or, e.g., a timestamp from a database. 

I've made a small change to the constructor, allowing the user to give the option 'masterTime' (a unix timestamp) in place of 'masterFile'. This makes the class far more useful IMO. I've also updated the docs in File.php.

E.g., to use a set of files as a master, you supply the max of the files' mtimes as 'masterTime'.

I'm currently using this patch in a rewrite of &quot;Minify&quot;, which combines, compresses, and serves CSS/Javascript files. If any of the files are modified, the 'masterTime' changes and the cache is invalidated.</pre>]]></content:encoded>
      <description><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by mrclay
2007-10-03T14:54:38+00:00
PHP: Irrelevant OS:  Package Version: 1.7.2

Description:
------------
Cache_Lite_File is convenient when your cache validity depends on a single file, but it can't help you if you want validity to depend on a set of files, or, e.g., a timestamp from a database. 

I've made a small change to the constructor, allowing the user to give the option 'masterTime' (a unix timestamp) in place of 'masterFile'. This makes the class far more useful IMO. I've also updated the docs in File.php.

E.g., to use a set of files as a master, you supply the max of the files' mtimes as 'masterTime'.

I'm currently using this patch in a rewrite of &quot;Minify&quot;, which combines, compresses, and serves CSS/Javascript files. If any of the files are modified, the 'masterTime' changes and the cache is invalidated.</pre>]]></description>
      <dc:date>2007-10-03T14:54:38+00:00</dc:date>
      <dc:creator>steve &amp;#x61;&amp;#116; mrclay &amp;#x64;&amp;#111;&amp;#x74; org</dc:creator>
      <dc:subject>Cache_Lite Feature/Change Request</dc:subject>
    </item>
    <item rdf:about="http://pear.php.net/bug/10502">
      <title>Cache_Lite: Feature/Change Request 10502 [Open] Cache_Lite_Function::call should accept standard callbacks as 1st argument</title>
      <link>http://pear.php.net/bugs/10502</link>
      <content:encoded><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by mrclay
2007-03-26T01:44:34+00:00
PHP: Irrelevant OS:  Package Version: CVS

Description:
------------
A tiny patch (below) would allow Cache_Lite_Function::call() to accept all standard callbacks for the target function. Currently call() fails to handle static method callbacks because it assumes all arrays passed in are instance methods. 

This should allow this method to play better with others (may resolve bug 660) and might even slightly improve perf. (I ab-ed bench3.php (-c 10 -n 1000) and didn't really see a difference)

Eventually requiring only standard callbacks would eliminate the entire if block.

Test script:
---------------
129,132c129,130
&lt;                 // in this case, $target is for example array($obj, 'method')
&lt;                 $object = $target[0];
&lt;                 $method = $target[1];
&lt;                 $result = call_user_func_array(array(&amp;$object, $method), $arguments);
---
&gt;                 // callback pseudotype
&gt;                 $result = call_user_func_array($target, $arguments);</pre>]]></content:encoded>
      <description><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by mrclay
2007-03-26T01:44:34+00:00
PHP: Irrelevant OS:  Package Version: CVS

Description:
------------
A tiny patch (below) would allow Cache_Lite_Function::call() to accept all standard callbacks for the target function. Currently call() fails to handle static method callbacks because it assumes all arrays passed in are instance methods. 

This should allow this method to play better with others (may resolve bug 660) and might even slightly improve perf. (I ab-ed bench3.php (-c 10 -n 1000) and didn't really see a difference)

Eventually requiring only standard callbacks would eliminate the entire if block.

Test script:
---------------
129,132c129,130
&lt;                 // in this case, $target is for example array($obj, 'method')
&lt;                 $object = $target[0];
&lt;                 $method = $target[1];
&lt;                 $result = call_user_func_array(array(&amp;$object, $method), $arguments);
---
&gt;                 // callback pseudotype
&gt;                 $result = call_user_func_array($target, $arguments);</pre>]]></description>
      <dc:date>2014-05-10T14:48:00+00:00</dc:date>
      <dc:creator>steve &amp;#x61;&amp;#116; mrclay &amp;#x64;&amp;#111;&amp;#x74; org</dc:creator>
      <dc:subject>Cache_Lite Feature/Change Request</dc:subject>
    </item>
</rdf:RDF>
