<?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&amp;PHPSESSID=6sh8hov6085gl1gd4s43b0k8h0</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/15902" />
      <rdf:li rdf:resource="http://pear.php.net/bug/14294" />
      <rdf:li rdf:resource="http://pear.php.net/bug/11227" />
      <rdf:li rdf:resource="http://pear.php.net/bug/11226" />
      <rdf:li rdf:resource="http://pear.php.net/bug/11225" />

     </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/15902">
      <title>Cache: Bug 15902 [Open] mkdir should do that recursive</title>
      <link>http://pear.php.net/bugs/15902</link>
      <content:encoded><![CDATA[<pre>Cache Bug
Reported by cweiske
2009-02-16T08:13:26+00:00
PHP: 5.2.8 OS:  Package Version: 

Description:
------------
   mkdir() in pear/Cache/Container/file.php:120 fails when the parent directory does not exist. Using recursive mkdir (third parameter true) solves that.

Test script:
---------------
      

Expected result:
----------------
      

Actual result:
--------------</pre>]]></content:encoded>
      <description><![CDATA[<pre>Cache Bug
Reported by cweiske
2009-02-16T08:13:26+00:00
PHP: 5.2.8 OS:  Package Version: 

Description:
------------
   mkdir() in pear/Cache/Container/file.php:120 fails when the parent directory does not exist. Using recursive mkdir (third parameter true) solves that.

Test script:
---------------
      

Expected result:
----------------
      

Actual result:
--------------</pre>]]></description>
      <dc:date>2009-02-16T08:14:08+00:00</dc:date>
      <dc:creator>cweiske &amp;#x61;&amp;#116; php &amp;#x64;&amp;#111;&amp;#x74; net</dc:creator>
      <dc:subject>Cache Bug</dc:subject>
    </item>
    <item rdf:about="http://pear.php.net/bug/14294">
      <title>Cache: Feature/Change Request 14294 [Open] Higher default highwater for Cache_Graphics</title>
      <link>http://pear.php.net/bugs/14294</link>
      <content:encoded><![CDATA[<pre>Cache Feature/Change Request
Reported by amay
2008-07-04T19:40:29+00:00
PHP: Irrelevant OS:  Package Version: 1.5.5RC4

Description:
------------
1) I recommend to use a greater default highwater set for Cache_Graphics than 2 MB because this is fairly small for images.

2) It would be nice if one could set the highwater mark in the Cache_Graphics constructor.

Expected result:
----------------
&gt; 2 MB highwater

If you want to be conservative, I think 32 MB would be a good choice, maybe 500 MB otherwise

Actual result:
--------------
2 MB highwater</pre>]]></content:encoded>
      <description><![CDATA[<pre>Cache Feature/Change Request
Reported by amay
2008-07-04T19:40:29+00:00
PHP: Irrelevant OS:  Package Version: 1.5.5RC4

Description:
------------
1) I recommend to use a greater default highwater set for Cache_Graphics than 2 MB because this is fairly small for images.

2) It would be nice if one could set the highwater mark in the Cache_Graphics constructor.

Expected result:
----------------
&gt; 2 MB highwater

If you want to be conservative, I think 32 MB would be a good choice, maybe 500 MB otherwise

Actual result:
--------------
2 MB highwater</pre>]]></description>
      <dc:date>2008-07-04T19:40:29+00:00</dc:date>
      <dc:creator>andimayer82 &amp;#x61;&amp;#116; gmail &amp;#x64;&amp;#111;&amp;#x74; com</dc:creator>
      <dc:subject>Cache Feature/Change Request</dc:subject>
    </item>
    <item rdf:about="http://pear.php.net/bug/11227">
      <title>Cache: Feature/Change Request 11227 [Open] php_mode variant of Container_file</title>
      <link>http://pear.php.net/bugs/11227</link>
      <content:encoded><![CDATA[<pre>Cache Feature/Change Request
Reported by didi0dmc
2007-06-05T02:56:44+00:00
PHP: Irrelevant OS:  Package Version: 1.5.5RC4

Description:
------------
We may be able to get improved read performance of cache files (on the possible expense of slower writes), if we add another &quot;mode&quot; of operation to Container/file.php:

(some pseudo code:)
Instead of doing
$cachedata = $this-&gt;decode(fread($fh, filesize($file)));

the read could be implemented as:
$cachedata = include($file);

The save method would accordingly use something like:
$cachedata = `var_export(func_get_arg(0), true)`;

Obviously objects in the input data would have to be serialized first, this is probably the only real drawback.</pre>]]></content:encoded>
      <description><![CDATA[<pre>Cache Feature/Change Request
Reported by didi0dmc
2007-06-05T02:56:44+00:00
PHP: Irrelevant OS:  Package Version: 1.5.5RC4

Description:
------------
We may be able to get improved read performance of cache files (on the possible expense of slower writes), if we add another &quot;mode&quot; of operation to Container/file.php:

(some pseudo code:)
Instead of doing
$cachedata = $this-&gt;decode(fread($fh, filesize($file)));

the read could be implemented as:
$cachedata = include($file);

The save method would accordingly use something like:
$cachedata = `var_export(func_get_arg(0), true)`;

Obviously objects in the input data would have to be serialized first, this is probably the only real drawback.</pre>]]></description>
      <dc:date>2007-06-05T02:56:44+00:00</dc:date>
      <dc:creator>dieter &amp;#x64;&amp;#111;&amp;#x74; rothacker &amp;#x61;&amp;#116; dmc &amp;#x64;&amp;#111;&amp;#x74; de</dc:creator>
      <dc:subject>Cache Feature/Change Request</dc:subject>
    </item>
    <item rdf:about="http://pear.php.net/bug/11226">
      <title>Cache: Feature/Change Request 11226 [Open] Proposal for memcached container driver</title>
      <link>http://pear.php.net/bugs/11226</link>
      <content:encoded><![CDATA[<pre>Cache Feature/Change Request
Reported by didi0dmc
2007-06-05T02:43:17+00:00
PHP: Irrelevant OS:  Package Version: 1.5.5RC4

Description:
------------
To get an implementation of a performant in-memory cache, even for large server clusters, I propose a driver which interfaces to memcached.

&quot;memcached is a high-performance, distributed memory object caching system, generic in nature, but intended for use in speeding up dynamic web applications by alleviating database load.&quot;

http://en.wikipedia.org/wiki/Memcached</pre>]]></content:encoded>
      <description><![CDATA[<pre>Cache Feature/Change Request
Reported by didi0dmc
2007-06-05T02:43:17+00:00
PHP: Irrelevant OS:  Package Version: 1.5.5RC4

Description:
------------
To get an implementation of a performant in-memory cache, even for large server clusters, I propose a driver which interfaces to memcached.

&quot;memcached is a high-performance, distributed memory object caching system, generic in nature, but intended for use in speeding up dynamic web applications by alleviating database load.&quot;

http://en.wikipedia.org/wiki/Memcached</pre>]]></description>
      <dc:date>2007-09-21T06:04:30+00:00</dc:date>
      <dc:creator>dieter &amp;#x64;&amp;#111;&amp;#x74; rothacker &amp;#x61;&amp;#116; dmc &amp;#x64;&amp;#111;&amp;#x74; de</dc:creator>
      <dc:subject>Cache Feature/Change Request</dc:subject>
    </item>
    <item rdf:about="http://pear.php.net/bug/11225">
      <title>Cache: Feature/Change Request 11225 [Open] Garbage collection Container_file improvement</title>
      <link>http://pear.php.net/bugs/11225</link>
      <content:encoded><![CDATA[<pre>Cache Feature/Change Request
Reported by didi0dmc
2007-06-05T02:31:03+00:00
PHP: Irrelevant OS:  Package Version: 1.5.5RC4

Description:
------------
To improve the expensive Garbage Collection procedure of Container_file (opening each cache file and reading the expiry date from the file content), there are two possibilities:

1. put the expiry date into the filename and do only directory reads for GC

2. calculate the expiry date from the ctime of each file. This also needs no opening of the cache files

Method 2 is probably &quot;nicer&quot;, since it does not change the naming convention of cache files.</pre>]]></content:encoded>
      <description><![CDATA[<pre>Cache Feature/Change Request
Reported by didi0dmc
2007-06-05T02:31:03+00:00
PHP: Irrelevant OS:  Package Version: 1.5.5RC4

Description:
------------
To improve the expensive Garbage Collection procedure of Container_file (opening each cache file and reading the expiry date from the file content), there are two possibilities:

1. put the expiry date into the filename and do only directory reads for GC

2. calculate the expiry date from the ctime of each file. This also needs no opening of the cache files

Method 2 is probably &quot;nicer&quot;, since it does not change the naming convention of cache files.</pre>]]></description>
      <dc:date>2007-06-05T02:31:03+00:00</dc:date>
      <dc:creator>dieter &amp;#x64;&amp;#111;&amp;#x74; rothacker &amp;#x61;&amp;#116; dmc &amp;#x64;&amp;#111;&amp;#x74; de</dc:creator>
      <dc:subject>Cache Feature/Change Request</dc:subject>
    </item>
</rdf:RDF>
