As a long-time user of and fan of mod_perl, I would say that there is no good reason today to be building such a framework using it.
Use an existing framework and extend it to fit your needs. For example, if you use Dancer2 you handle sessions simply like this in the application config:
engines:
session:
Simple:
cookie_name: your_app.session
There are pre-built session engines for cookies, file, memcached, database, whatever you want.
Using a framework like this in no way prevents you from building tools to simplify menus, etc. But using a modern framework does mean that you will avoid lots of struggles and pain with dated libraries.
The way forward always starts with a minimal test.
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.