Re: Converting common subroutines as a module

by Fletch (Bishop)

on Nov 01, 2006 at 16:42 UTC ( [id://581703]=note: print w/replies, xml )

Need Help??

Lower case'd module names (e.g. "common") are reserved for Perl's internal use by convention.
It'd be better to create the CGI instance in the main body and pass that as an argument to your utility routines
You might consider using one of the frameworks like CGI::Application which provides functionality similar to this off-the-shelf

Comment on Re: Converting common subroutines as a module

Replies are listed 'Best First'.
Re^2: Converting common subroutines as a module by markjugg (Curate) on Nov 01, 2006 at 19:04 UTC
I second the CGI::Application recommendation. Through the website I linked to, you can find a list of a lot of plugins that are available, including some to Authentication and Authorization. I've been using this framework for years and have found it very helpful, and appropriate for all scales of projects. Mark Stosberg	[reply]
Re^3: Converting common subroutines as a module by Anonymous Monk on Nov 01, 2006 at 21:38 UTC
Thanks for the response. I will definitely look into CGI::Application for my website. I forgot to mention about an important aspect of my application. After authentication and path set-up, I also have some pages with non-cgi perl scripts( like reading data files to create data structures to be used in defining the UI). Presently, I have them as apart of the cgi script. Can I handle that portion as well using CGI::Application?	[reply]

Domain Nodelet^?

Node Status^?

node history
Node Type: note [id://581703]
help

Chatterbox^?

How do I use this? • Last hour • Other CB clients

Other Users^?

Others chilling in the Monastery: (2)

As of 2024-04-19 21:43 GMT

Sections^?

Information^?

Find Nodes^?

Leftovers^?

Voting Booth^?

No recent polls found