Re: Proposal: File_Apache
| From: | Mika Tuupola | Date: | Fri, 12 Sep 2003 14:35:56 +0000 |
| Subject: | Re: Proposal: File_Apache | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-21438@lists.php.net to get a copy of this message | ||
On Fri, 12 Sep 2003, Marshall Roch wrote:
> File_Apache seems to be a better name for a class that handles all of
> this Apache stuff
On the other hand. File_Passwd also handles CVS server
password so it would not fit into Apache category. I would
rather improve the existing password class than introduce
another one with almost identical functionality.
> File_HtAccess makes sense in this case. I had expressed interest in
> extending File_HtAccess to support mod_rewrite to Mika two days ago.
Which I agreed is a good idea. There just needs to be
a clean way to do it without bloating the base class.
At a quick glance I like the way Michael did it.
> The problem with File_HtAccess right now is that the base class handles
> authentication, which is not .htaccess's sole purpose. File_HtAccess, I
> think, should handle parsing (and validating?) the file, and writing
> new/modified directives to it.
Huh? File_HtAccess does not do any authentication. It parses
and writes .htaccess files and offer methods to add/modify
directives to it.
--
Mika Tuupola http://www.appelsiini.net/~tuupola/