-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On July 19, 2004 08:29 am, Kip Hampton wrote: > Michael A Nachbaur wrote: > > Essentially, this patch intends to add the "AxXMLCatalog" Apache > > directive which defines which XML catalogs to include into XML::LibXML. > > Might we not be better off creating a more generic AxXMLParserOpt > directive (that pushes onto a @list of key/value pairs)?
That isn't a bad idea. I've wanted for a while to take advantage of XML::LibXML's various configuration parameters, but have been reluctant to do so since I don't want to have an Ax* directive problem...but the XML catalogs bit was just too desirable to let be. So, if this is the direction everyone'd like to go (anyone?) the XML Catalog directive would look like so: AxXMLParserOpt XMLCatalog /catalog1.xml AxXMLParserOpt XMLCatalog /catalog2.xml AxXMLParserOpt MaxDepth 4500 etc... > Rationale: We already suffer from too many conf directives-- this adds > an important one-- but there are many others that people might want > access to as well. Do we really want to duplicate Ax* option for each > possible parser option? The answer is an obvious "no" but, then how do > we decide which ones to support/leave out? Might this be useful as well for instances like the recent XML::LibXSLT->max_depth discussion on the perl-xml mailing list? > Also, what if I'm not using XML::LibXML, is this option still relevant? > Aren't we setting ourselves up to create still more Ax* options for the > other parsers? Well, if another parser supports XML catalogs, presumably this same directive could be used for it as well. Its been such a long time since I played with Sablotron that it shouldn't even be considered as valid experience any more, so I'm not certain if it can use catalogs. - -- Michael A. Nachbaur <[EMAIL PROTECTED]> http://nachbaur.com/pgpkey.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFA+/g0vow0fXaFDZQRAm+6AJ9HHoTgWsvhyWGRzg4ih+MlsfiDuACeIT6W d72RpWp+X541ts/d4AC9Fo0= =c73v -----END PGP SIGNATURE-----
