Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
If i were you i'd look into CGI::Application ( tutorial here ) and cut the time down in half.

I'd also check out our tutorials section for an excellent HTML::Template tutorial, cause HTML::Template incorporates easily into CGI::Application.

You should also read Scaling single-script CGI applications

After you've read all of the above (or at least skimmed this and this), it should be more clear to you how to organize this.

Personally, i'd use base everything on CGI::Application, and have two scripts/packages, one for users, and one for administrators.

Since administrators would like to do a lot of the same things regular users would, i'd make the "administrator" package a subclass of the regular user package.

P.S. CGI::Application kind of forces (strong word) you into creating a module and inheriting from CGI::Application

update: here is an example of using CGI::Application along with File::Cache and cookies for session managment.

 
______crazyinsomniac_____________________________
Of all the things I've lost, I miss my mind the most.
perl -e "$q=$_;map({chr unpack qq;H*;,$_}split(q;;,q*H*));print;$q/$q;"


In reply to (crazyinsomniac) Re: Multiple tasks in same_script, or multiple_scripts? by crazyinsomniac
in thread Multiple tasks in same_script, or multiple_scripts? by joshua

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others musing on the Monastery: (6)
As of 2024-03-29 01:07 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found