plus some tests that use one (or both) of the Tie:: modules to make sure
that the mod_perl layer respects the ties. but yes, I think it's
essentially a user/documentation issue - I'm not too keen on using Tie::
modules behind everyone's back.
I agree with this, but if it could support array references too, that would go a long way toward eliminating the problem. This should be partially done already, since the Eagle book says (p. 417):
If a directive is repeated multiple times with different arguments
each time, you can represent it in an array of arrays. This example
using the AddIcon directive shows how: @AddIcon = (
[ '/icons/compressed.gif' => qw(.Z .z .gz .tgz .zip) ],
[ /icons/layout.gif' => qw(.html .shtml .htm .pdf) ]
);Now that shows just array references of simple lists, but if that could be extended a bit, then I could probably use my original example:
$Location = [ { "/data" => { SetHandler => 'default-handler' }},
{ "/data/preview" => {
SetHandler => 'perl-script',
PerlFixupHandler => 'Bric::App::PreviewHandler::fixup_handler',
PerlHandler => 'Bric::App::Handler'
}}
];
Or maybe it could work like this?
@Location = (
[ "/data" => SetHandler => 'default-handler' ],
[ "/data/preview" =>
SetHandler => 'perl-script',
PerlFixupHandler => 'Bric::App::PreviewHandler::fixup_handler',
PerlHandler => 'Bric::App::Handler'
]
);
Hrm. I'll have to try that. Think it'll work?
Regards,
David
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
