A compression wrapper like PDO would be great. And they do all do the same things more or less. Take data and compress it. Take compressed data and uncompress it. Not that different.
On 21/07/06, Pierre <[EMAIL PROTECTED]> wrote:
Hello, On 7/21/06, Ron Korving <[EMAIL PROTECTED]> wrote: > I was thinking the same thing. We can of course clutter the namespace with a > class for every possible file extension we want to develop an API for, but > maybe we can do the smart thing and do what PDO does for databases: present > a unified API. I was thinking the same as well. But I don't think it is a good idea. For the simple operations, you can do it easily in php. I don't think there is a need for an internal implementation of such wrappers. > I don't like the idea of having GZip, Zip, Rar, Arj, Etc classes when they > all do the same. They don't always do the same, that's the problem. Also I'm a fan of one need/one tool. PDO was needed because it is really a mess in the DB APIs. I would prefer to define some common API and have independent extensions. It will let us implement all format specific features or needs (which can be speed, compression level, etc.). Cheers, --Pierre -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
-- ----- Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!" -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
