Kip Hampton wrote:
Michael A Nachbaur wrote:
This adds a new configuration directive "AxDirHandler <Module>" which is used to indicate the desired directory handler plugin, but AxHandleDirs On|Off is still required to toggle if directory listings will be handled. If AxDirHandler is not specified, the default module Apache::AxKit::DirHandler::Basic is used (this is essentially a copy-and-paste job from the current directory handler, so backwards-compatibility is assured).
I'm generally +1 on this proposed patch (and thanks for taking this up, Mike).
It seems messy to add YA config directive for the special Provider case (AxDirHandler is really just a ContentProvider for dir listings) when setting the AxHandlerDir to On and applying the correct ContentProvider should work, but i guess we bought that when we made the AxHandleDir *flag* effect the content that was returned (rather than just signaling the intention to handle directory listings).
:-\
Yeah, I know. I don't like the extra directive either, but I can't really see a way around it. The problem is that there are circumstances where I want to serve content from two different directories with the same ContentProvider (A:A:P:File) but with different directory handlers.
In fact, I'm doing just that with Callisto (which was the impetus to get moving on this patch). I have one directory that uses the Basic plugin for rendering directory contents, while another generates RDF content for processing by a Mozilla treeview widget.
I'm certainly up for suggestions on this one however. I don't want to make an unpleasant situation worse (nor do I want to invalidate your book Kip ;-) but I don't see an immediately convenient way of working around this.
Ideas, suggestions, threats and bribes welcome. :-)
