comment on

First things first: I don't think the "perfect" framework for web applications has been invented yet, so ++ for giving it a shot.

One thing I don't like is that the template is too tightly coupled to the action - it's entirely possible that several related actions want to use the same template, or for an action to have more than one resulting template.

For instance:
form -> (submit action) -> form again, with missing data highlighted -> (submit action) -> confirmation screen.

By deriving the template name from the classname of the action you need to create extra templates that will probably only include the "real" template.

Also, I'm sceptical about using classes to describe actions. See my comment in the CGI::Prototype thread.

Lastly, I would like more hooks in the code - some place to do general setup or session management would be nice for instance (maybe by inheriting from the Apache::Controller). See CGI::Application and CGI::Prototype for examples :-)

"What should it profit a man, if he should win a flame war, yet lose his cool?"

In reply to Re: RFC: Apache::Controller by Joost
in thread RFC: Apache::Controller by revdiablo

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.