http://pear.php.net/bugs/search.php?cmd=display&package_name%5B0%5D=Cache Search Results en-us pear-webmaster@lists.php.net pear-webmaster@lists.php.net hourly 1 2000-01-01T12:00+00:00 http://pear.php.net/gifs/pearsmall.gif http://pear.php.net/bugs http://pear.php.net/bugs/20318 Cache Feature/Change Request Reported by midget 2014-06-26T19:38:44+00:00 PHP: Irrelevant OS: Debian GNU/Linux Package Version: 1.5.6 Description: ------------ Hi Team, This software is part of the Debian archive and will be removed from official repositories due to licensing issues (please, see below). Would you consider changing the license to another BSD style license? For reference see: * https://bugs.debian.org/752632 * https://bugs.debian.org/752642 * https://ftp-master.debian.org/REJECT-FAQ.html Extracted from: https://ftp-master.debian.org/REJECT-FAQ.html License PHP: --------------- You have a PHP add-on package (any php script/"app"/thing, not PHP itself) and it's licensed only under the standard PHP license. That license, up to the 3.x which is actually out, is not really usable for anything else than PHP itself. I've mailed our -legal list about that and got only one response, which basically supported my view on this. Basically this license talks only about PHP, the PHP Group, and includes Zend Engine, so its not applicable to anything else. And even worse, older versions include the nice ad-clause. One good solution here is to suggest a license change to your upstream, as they clearly wanted a free one. LGPL or BSD seems to be what they want. Thanks in advance.]]> Cache Feature/Change Request Reported by midget 2014-06-26T19:38:44+00:00 PHP: Irrelevant OS: Debian GNU/Linux Package Version: 1.5.6 Description: ------------ Hi Team, This software is part of the Debian archive and will be removed from official repositories due to licensing issues (please, see below). Would you consider changing the license to another BSD style license? For reference see: * https://bugs.debian.org/752632 * https://bugs.debian.org/752642 * https://ftp-master.debian.org/REJECT-FAQ.html Extracted from: https://ftp-master.debian.org/REJECT-FAQ.html License PHP: --------------- You have a PHP add-on package (any php script/"app"/thing, not PHP itself) and it's licensed only under the standard PHP license. That license, up to the 3.x which is actually out, is not really usable for anything else than PHP itself. I've mailed our -legal list about that and got only one response, which basically supported my view on this. Basically this license talks only about PHP, the PHP Group, and includes Zend Engine, so its not applicable to anything else. And even worse, older versions include the nice ad-clause. One good solution here is to suggest a license change to your upstream, as they clearly wanted a free one. LGPL or BSD seems to be what they want. Thanks in advance.]]> 2014-06-26T19:38:44+00:00 midget at midworld dot net Cache Feature/Change Request http://pear.php.net/bugs/20124 Cache Documentation Problem Reported by midget 2013-11-07T18:35:59+00:00 PHP: Irrelevant OS: Debian GNU/Linux Package Version: 1.5.6 Description: ------------ Hi, The package license was upgraded to PHP 3.01, but contained files still reads: License PHP v2.0 wich is not GPL copmpliant. Cache-1.5.6/Application.php: PHP (v2.02) Cache-1.5.6/Cache.php: PHP (v2.0) Cache-1.5.6/Container.php: PHP (v2.0) Cache-1.5.6/Error.php: PHP (v2.0) Cache-1.5.6/Function.php: PHP (v2.0) Cache-1.5.6/Graphics.php: PHP (v2.0) Cache-1.5.6/HTTP_Request.php: PHP (v2.0) Cache-1.5.6/Output.php: PHP (v2.0) Cache-1.5.6/OutputCompression.php: PHP (v2.0) Please, update licenses in file headers. Thanks in advance. Regards,]]> Cache Documentation Problem Reported by midget 2013-11-07T18:35:59+00:00 PHP: Irrelevant OS: Debian GNU/Linux Package Version: 1.5.6 Description: ------------ Hi, The package license was upgraded to PHP 3.01, but contained files still reads: License PHP v2.0 wich is not GPL copmpliant. Cache-1.5.6/Application.php: PHP (v2.02) Cache-1.5.6/Cache.php: PHP (v2.0) Cache-1.5.6/Container.php: PHP (v2.0) Cache-1.5.6/Error.php: PHP (v2.0) Cache-1.5.6/Function.php: PHP (v2.0) Cache-1.5.6/Graphics.php: PHP (v2.0) Cache-1.5.6/HTTP_Request.php: PHP (v2.0) Cache-1.5.6/Output.php: PHP (v2.0) Cache-1.5.6/OutputCompression.php: PHP (v2.0) Please, update licenses in file headers. Thanks in advance. Regards,]]> 2018-04-19T12:32:19+00:00 midget at midworld dot net Cache Documentation Problem http://pear.php.net/bugs/14294 Cache Feature/Change Request Reported by amay 2008-07-05T00: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: ---------------- > 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]]> Cache Feature/Change Request Reported by amay 2008-07-05T00: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: ---------------- > 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]]> 2008-07-05T00:40:29+00:00 andimayer82 at gmail dot com Cache Feature/Change Request http://pear.php.net/bugs/11227 Cache Feature/Change Request Reported by didi0dmc 2007-06-05T07: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 "mode" of operation to Container/file.php: (some pseudo code:) Instead of doing $cachedata = $this->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.]]> Cache Feature/Change Request Reported by didi0dmc 2007-06-05T07: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 "mode" of operation to Container/file.php: (some pseudo code:) Instead of doing $cachedata = $this->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.]]> 2007-06-05T07:56:44+00:00 dieter dot rothacker at dmc dot de Cache Feature/Change Request http://pear.php.net/bugs/11225 Cache Feature/Change Request Reported by didi0dmc 2007-06-05T07: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 "nicer", since it does not change the naming convention of cache files.]]> Cache Feature/Change Request Reported by didi0dmc 2007-06-05T07: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 "nicer", since it does not change the naming convention of cache files.]]> 2007-06-05T07:31:03+00:00 dieter dot rothacker at dmc dot de Cache Feature/Change Request