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 don't like the idea of having GZip, Zip, Rar, Arj, Etc classes when they 
all do the same. In the end people will start realizing the PDO-road 
should've been taken from day one. I wish I had any experience with PECL to 
work something out right now, but I don't. If anyone's interested, I'd be 
willing to invest some time in constructing an API though (as a sort of 
first step in a proof of concept).

- Ron


""Jared Williams"" <[EMAIL PROTECTED]> schreef in bericht 
news:[EMAIL PROTECTED]
>
>> Many people (incl. php devs) asked me if I can include zip in 5.2.0.
>> Ilia thought it was too late in the game and planed to do it in 5.2.1.
>>
>> I like to have it in, as experimental.
>>
>> Please note that it intoduces a new class called Zip, but I
>> never saw a
>> php zip implementation named Zip.
>>
>> +1/-1/0?
>
> I would've preferred an unified package for handling multiple archives
> (zip/rar/tgz etc).
> Similar to what PDO does for databases, if it is going into core.
>
> Jared 

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to