Re: Proposal: File_Apache

> # HtPasswd: > This class manages Apache's AuthUserFiles with Apache's htpasswd > executable. It supplies an easy way to add user with passwords, > change passwords of users and verify passwords. > But there are two limitations deriving from htpasswd and encryption: > o DES is not available on Win32 > o MD5 passwords cannot be verified Have you taken a look at the Auth package with the type file ? IIRC, it can do almost all the things you're mentioning here. I also heard some mentioning of being able to add users to the file via this package, though that code was still being develipped, IIRC. > # HtAccess: > Of course this class is for Apache's AccessFiles commonly known > as .htaccess files, with the ability of creating restricted > areas, setting desireable php options and other commonly used > directives supplied by Apache. > I know there's already a class called File_HtAccess, but I didn't > know that when I wrote mine (though some time ago). Also have a > look at the features. Comparing it to File_HtAccess, what exactly does this class do that the other pear package didn't? I havn't used that ackage in some time, though I remember it focussing more on the resitrcted areas part of what you made here. Curiosity makes me ask however, what can yours do that the other can't, and vice-versa? > http://dev.iworks.at/php/PEAR/File/.source?file=Apache > http://dev.iworks.at/php/PEAR/File/.source?file=Apache/HtAccess > http://dev.iworks.at/php/PEAR/File/.source?file=Apache/HtPasswd > http://dev.iworks.at/php/PEAR/File/.source?file=Apache/HtGroup Browsed it briefly, code looks nice and clean from what I could see. Cipriano