Re: Proposal: File_Apache

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Mika Tuupola, you wrote: >> +- 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. Hm? I think I'm missin' sth... > 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(). If that becomes the way to go I would be happy to provide File_HtGroup. BTW: I found a type in this class, files are updated. > File_Passwd already does this and it does not need > the htpasswd binary. I'm sorry, I didn't have it locally, but viewing it know I have to say, that it only supports crypt() which is not available for Apache under Win32. > 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? > I'm happy to hear that from der lead-dev, perhaps we can find some consense :) Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (Cygwin) iD8DBQE/YdS83645gzRPvy8RAmJtAJ40fr9TFPblMBGL9/1wMqBnMihogACeIAz5 AY5YhoOiQHhPdj5S6BqqCV0= =3syM -----END PGP SIGNATURE-----