RE: A "catch-all" component?

Thanks for the tip. However, after reading up the documentation, I think
that subclassing HTML::Mason::Resolver
will do exactly what I want (and I want something similar to mod_rewrite for
components) I'll post an announce
after I have my module finished.

Egor.

>       See http://masonhq.com/docs/manual/Devel.html#subrequests and
> take a look at the out_method parameter. If you pass 'out_method =>
> \$buffer' then $buffer will contain the output of the subrequest.
>       Depending on what kind of use you are putting this to, however,
> it seems like the wrong way to go about it. If you want overridable
> behavior, then using methods is probably going to give you more
> flexibility. If you need to be able to handle arbitrary calls to paths
> that don't exist, then dhandlers make sense. If, on the other hand, you
> just want a shorthand way of calling components whose paths are
> otherwise too long, then maybe you should just move those components to
> a shorter path. :)
>               Ben
>



-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0