i think CGI::Application is great. Really great.

But I never use it. For similar reasons that you wrote Apllication::Pipeline.

but heres the thing; I can write my own baseclass framework that suits my applications perfectly.
And put in whatever handlers/plugins/doodahs i need, when i need them.

Application::Pipeline seems like a pretty neat module; I am not dissing that at all. But I see a fundamental flaw with these "just add water" frameworks; the choice between:

• warping my code round an insufficent framework
• importing and wading through a bunch of generic stuff i dont need
• spending a morning hacking a custom-fit solution

is no choice at all. Know what I mean?

update: what i mean is: IMO there is no happy medium between a simple or bloated "Application Framework". And the general mechanisms involved are too simple to appeal to compromise in the name of "Code-Reuse".

---

---

• 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.