“What other knowledge is assumed before using a Mojolicious or Dancer? I ask this as much for myself as for Steve. I know that these tools abstract a lot of what CGI, mod_perl or FCGI do but when I look at the tutorial listing there's honestly a few things... Ok more than a few things on there that I'm either not familiar with or don't know very well. What would be a good way to approach a Mojolicious assuming little to no previous experience building web applications?”
A Rough List of Prerequisites So Far:
- HTTP Headers
- Model Viewer Controller: *(Also referred to as a separation of concerns e.g.: between presentation layer, business logic layer, data access layer, database layer)
- HTML
- Perl
- Relational Database System (Or at least knowledge of how databases work in general)
Before I get (deservedly?) slammed for stating the painfully obvious, understand again that this is what one would suggest to a new Perl user who has little to no experience with web applications. (I'll go ahead and include myself in this group.) The questions get asked more and more here that are either:
- Which of the new frameworks should I use?
- Do I still need to know CGI?
- Lastly: I just started learning Perl, how do I build XYZ logic for my web application?
That last one concerns me personally. In the referenced parent thread above, I suggested to Steve that he check out Melody (CGI::Application), CGI::FormBuilder and the CGI 101 Free chapters to get started. Those are mature peer reviewed resources that provide good, effective solutions — right? I know that I appreciate having lots of different options but there is definitely a 'New' vs 'Old' way to do it that sometimes (IMHO) teeters towards 'Correct' vs 'Wrong'.
What direction, without a 'One True Way' manifesto, do we give new Perl programmers looking to develop web applications?
Luis
* UPDATE (Same Day): Corrected the example defining (SoC) Separation of Concerns to include: (...presentation layer, business logic layer, data access layer, database layer) from the original (Data, Business Logic and Presentation.). The example is pulled from the Separation of concerns Wikipedia entry. Thanks to davido for the heads up.
"...the adversities born of well-placed thoughts should be considered mercies rather than misfortunes." — Don Quixote
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.