Thanks for valuable input, I'll respond below..
On tirsdag, feb 25, 2003, at 18:17 Europe/Oslo, Dave Rolsky wrote:
On Tue, 25 Feb 2003, Marcus Ramberg wrote:
It probably goes about the wrong way to do some stuff, but it works for
me. It's somewhat untested besides that though, so I'd love to hear
from anyone who's got comments. It's a bit unfinished, most
notoriously, it's missing a test suite, but no real show stoppers that
I see.
A couple things.
First, let Mason (and Class::Container) do more work for you. Add this to
valid_params:
par_static_directory_index => { type => ARRAYREF,
default => [ qw( index.htm index.html ) ],
},
Yeah, It's on the todo :) I looked at how Apache::PAR::Static implemented it, and used that approach. lazy
This will handle a directive called MasonParStaticDirectoryIndex for you.
I'm not sure why you add this parameter when you call HTML::Mason::ComponentSource->new:
extra => { comp_root => 'par' },
There was a really good reason for that, either to get the dhandler or the autohandler to work, uhm, but I really don't remember why.. I did quite some reading in the mason classes, and wanted behavior required a comp_root to be set. Or maybe it just got very late and something else fixed it :) I'll look into it.
<snip>
Finally, I'm not sure this actually has all that much to do with PAR, since you don't use it internally (just Archive::Zip). Maybe you can document the relationship, and how this might work with a Mason application distributed as a par-ball.
Yeah, more documentation is forthcoming. This is for use with Apache::PAR, and Apache::PAR uses Archive::Zip internally as well. (for loading non-libraries).
Marcus
------------------------------------------------------------------------ everything about me @ http://thefeed.no/marcus/
