<?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/16591" />
      <rdf:li rdf:resource="http://pear.php.net/bug/16119" />
      <rdf:li rdf:resource="http://pear.php.net/bug/14636" />
      <rdf:li rdf:resource="http://pear.php.net/bug/14441" />
      <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/16591">
      <title>Cache_Lite: Feature/Change Request 16591 [Open] Touch cache files on regeneration to prevent &quot;stampeding&quot;</title>
      <link>http://pear.php.net/bugs/16591</link>
      <content:encoded><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by tacker
2009-09-10T16:14:39+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 1.7.8

Description:
------------
See http://www.4pmp.com/2009/09/pear-cache_lite-preventing-stampeding/</pre>]]></content:encoded>
      <description><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by tacker
2009-09-10T16:14:39+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 1.7.8

Description:
------------
See http://www.4pmp.com/2009/09/pear-cache_lite-preventing-stampeding/</pre>]]></description>
      <dc:date>2009-09-10T16:14:39+00:00</dc:date>
      <dc:creator>tacker &amp;#x61;&amp;#116; php &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/16119">
      <title>Cache_Lite: Feature/Change Request 16119 [Open] Count cache entries cleaned</title>
      <link>http://pear.php.net/bugs/16119</link>
      <content:encoded><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by farell
2009-04-18T13:46:57+00:00
PHP: 5.2.9 OS:  Package Version: 1.7.7

Description:
------------
With current API, we can clear a cache with Cache_Lite::clean and only notified if the clean is OK (true) or KO (false).

I appreciate instead of a boolean return value, to get count of files removed.

That will allow to application that used Cache_Lite to print something like PEAR did when you run command pear clear-cache

reading directory &lt;cache_dir_name&gt;
&lt;count&gt; cache entries cleared

Expected result:
----------------
return &lt;count&gt; cache entries cleared



Actual result:
--------------
return true if cache clean and false otherwise</pre>]]></content:encoded>
      <description><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by farell
2009-04-18T13:46:57+00:00
PHP: 5.2.9 OS:  Package Version: 1.7.7

Description:
------------
With current API, we can clear a cache with Cache_Lite::clean and only notified if the clean is OK (true) or KO (false).

I appreciate instead of a boolean return value, to get count of files removed.

That will allow to application that used Cache_Lite to print something like PEAR did when you run command pear clear-cache

reading directory &lt;cache_dir_name&gt;
&lt;count&gt; cache entries cleared

Expected result:
----------------
return &lt;count&gt; cache entries cleared



Actual result:
--------------
return true if cache clean and false otherwise</pre>]]></description>
      <dc:date>2009-04-18T13:46:57+00:00</dc:date>
      <dc:creator>pear &amp;#x61;&amp;#116; laurent-laville &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/14636">
      <title>Cache_Lite: Bug 14636 [Open] Intermitent bugs during autocleaning and reading</title>
      <link>http://pear.php.net/bugs/14636</link>
      <content:encoded><![CDATA[<pre>Cache_Lite Bug
Reported by tom75
2008-09-11T02:00:42+00:00
PHP: 5.2.5 OS:  Package Version: 1.7.4

Description:
------------
I have sometimes this bug during autocleaning :
[warning] [/www/sources/cache_lite/Lite.php (Line 581)] unlink(/www/html/temp/cache_4/cache_48/cache_a7b2dab44b5ee1981fe92e12229db431_142f2ae86596fff5b9754e337519b742) [function.unlink]: No such file or directory

Intermitent bug :
[warning] [/www/sources/cache_lite/Lite.php (Line 724)] fread() [function.fread]: Length parameter must be greater than 0</pre>]]></content:encoded>
      <description><![CDATA[<pre>Cache_Lite Bug
Reported by tom75
2008-09-11T02:00:42+00:00
PHP: 5.2.5 OS:  Package Version: 1.7.4

Description:
------------
I have sometimes this bug during autocleaning :
[warning] [/www/sources/cache_lite/Lite.php (Line 581)] unlink(/www/html/temp/cache_4/cache_48/cache_a7b2dab44b5ee1981fe92e12229db431_142f2ae86596fff5b9754e337519b742) [function.unlink]: No such file or directory

Intermitent bug :
[warning] [/www/sources/cache_lite/Lite.php (Line 724)] fread() [function.fread]: Length parameter must be greater than 0</pre>]]></description>
      <dc:date>2008-10-26T10:58:18+00:00</dc:date>
      <dc:creator>thomas &amp;#x61;&amp;#116; aina &amp;#x64;&amp;#111;&amp;#x74; fr</dc:creator>
      <dc:subject>Cache_Lite Bug</dc:subject>
    </item>
    <item rdf:about="http://pear.php.net/bug/14441">
      <title>Cache_Lite: Feature/Change Request 14441 [Open] Allow more flexible control over permissions and groups of files and dirs</title>
      <link>http://pear.php.net/bugs/14441</link>
      <content:encoded><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by tacker
2008-08-03T07:58:46+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 1.7.4

Description:
------------
Reported by TheRealAL [at] gmail [dot] com

Hello!
I have developed patch to package Cache/Lite that allows more flexible control over permissions and groups of files and directories in cache.

Added settings are _hashedDirectoryGroup, _cacheFileMode,
_cacheFileGroup.

Also, I think it's not right to name setting _hashedDirectoryUmask - it's not umask(2), it's directory's access rights, so I renamed it to _hashedDirectoryMode.

p.s. patch is not common - it works only on *nix systems, also we have restriction in chgrp: users may change the group of a file to any group of which that user is a member. Patch just suitable for my project, but I think I must give my changes back to community.</pre>]]></content:encoded>
      <description><![CDATA[<pre>Cache_Lite Feature/Change Request
Reported by tacker
2008-08-03T07:58:46+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 1.7.4

Description:
------------
Reported by TheRealAL [at] gmail [dot] com

Hello!
I have developed patch to package Cache/Lite that allows more flexible control over permissions and groups of files and directories in cache.

Added settings are _hashedDirectoryGroup, _cacheFileMode,
_cacheFileGroup.

Also, I think it's not right to name setting _hashedDirectoryUmask - it's not umask(2), it's directory's access rights, so I renamed it to _hashedDirectoryMode.

p.s. patch is not common - it works only on *nix systems, also we have restriction in chgrp: users may change the group of a file to any group of which that user is a member. Patch just suitable for my project, but I think I must give my changes back to community.</pre>]]></description>
      <dc:date>2008-08-03T07:58:46+00:00</dc:date>
      <dc:creator>m &amp;#x61;&amp;#116; tacker &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-03T14: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-03T14: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-03T14: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-03T09: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-03T09: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-03T09: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 [Assigned] 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-25T20: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-25T20: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>2008-03-31T13:22:40+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>
