Re: Proposal: File_Apache

Cipriano Groenendal wrote:

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?

File_Apache seems to be a better name for a class that handles all of this Apache stuff. .htaccess really needs .htpasswd and .htgroup to use authentication, so it makes sense to have it all in the same package. On the other hand, mod_rewrite needs .htaccess, so extending File_HtAccess makes sense in this case. I had expressed interest in extending File_HtAccess to support mod_rewrite to Mika two days ago. 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. Then File_HtAccess_Auth can do authentication and File_HtAccess_Rewrite can handle mod_rewrite. I wonder if combining the two packages (keeping File_HtAccess's API in File_Apache so users just need to switch out the packages) and bringing in Mika as a developer would work? -- Marshall Roch http://pear.php.net/user/mroch