Hello, > Yes, this would also be a good "excuse" to finally document the merging > behaviour of directives (e.g. AddType's are merged between vhosts, but > ServerName overrides the main server definition). > > The above description should also describe the argument(s) of the > directive, such that a GUI could ask for input in the appropriate way. > > You'd also want to be able to note that some directives can be repeated > multiple times to build up "tables" of arguments. For example, AddHandler > can be repeated to build up a table of extension-to-handler mappings, so > you would (probably) want to configure this via an on-screen list with > options to add/remove/edit entries.
Yes. I do it right now defining list and list2 types list if you can have something like directive arg1 arg2 ar3... and list2 if directive arg1 directive arg2... Then I put the arguments in a table where you can add/edit/delete like you said before > So perhaps an extension to the above like this: > > <directive> > <name>AddType</name> > <description>Map file extension to MIME-type</description> > <context>main_server virtual_host per-directory</context> > <override>fileinfo</override> > <arguments> > <el><name>Handler</name> > <type>text[100]</type> > </el> > <el> > <name>Extension</name> > <type>text[20]</type> > </el> > </arguments> > <repeat>table-append</repeat> > <merging>table-append</merging> > </directive> I would be interested in knowing how does each module tells the parser which are their arguments in Apache and how what knows what it has to append and override, etc Could this be extracted from the source code or a running Apache or it is precisely what having this XML definition would allow? Best regards Daniel -- ----------------------------------------------------------------------------- Daniel Lopez Ridruejo "Audaces fortuna juvat" E-Mail: [EMAIL PROTECTED] -----------------------------------------------------------------------------
