Re: Proposal: File_Apache

On Fri, 12 Sep 2003, Michael Wallner wrote: > > 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... Apache is not the only webserver which uses .htaccess and friends. Atleast NCSA httpd and probably other use them. Thus naming them after apache is not appropriate. > > 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. Great. We still need to hear what others think. > 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. Maybe File_Passwd should be improved? Must say I am not too familiar with PHP in Windows. > > 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 :) Sure :) -- Mika Tuupola http://www.appelsiini.net/~tuupola/