Re: Proposal: File_Apache

On Fri, 12 Sep 2003, Michael Wallner wrote: > /File > | > +- Apache.php - just a container with a factory method > +- /Apache > | > +- HtAccess.php - operates on .htaccess files > +- HtPasswd.php - operates on .htpasswd files > +- HtGroup.php - operates on .htgroup files Usage of these files are not limited to Apache web server. Thus naming it File_Apache might not be appropriate. > # HtGroup: > This class just manages Apache's AuthGroupFiles in a very simple > manner, with the ability to add/change/delete users and groups. This looks fine. It could be included in PEAR as File_HtGroup. What I would do is to change some method names to be similar with File_HtAccess. For example parse() -> load() and commit() -> save(). > # 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 File_Passwd already does this and it does not need the htpasswd binary. > # 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. There already is File_HtAccess. However I like the extra functionality your version has. Some of it could (should :) be included in the current File_HtAccess? -- Mika Tuupola http://www.appelsiini.net/~tuupola/