Hey Greg -- > How is this different than using mode_param() with a callback method?
It's very similar, but it provides two big improvements: First, it allows you to NOT use mode_param(\&sub) when all you want to do is to stack behaviors. Second, cgiapp_prerun() can be used with inheritance. With mode_param(\&sub), it's an all-or-nothing proposition. If you use it, you have to totally implement your own state machine. With cgiapp_prerun() you can use CGI-App's state machine, but selectively add behaviors under specific conditions. It is probably better to use mode_param(\&sub) in cases where you truly want to swap in your own state-management engine. In cases where you are mostly happy with CGI-App's internal state-management behavior, adding cgiapp_prerun() will allow you to extend via a custom super-class. TTYL, -Jesse- --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
