[TAG] Pointers to Perl CGI Resources
rus.cahimb at gmail.com
Thu Oct 26 19:18:55 MSD 2006
> You seem to be skirting around a more fundamental problem: not knowing
> where to start. If this is the case, it makes me wonder just how
> efficient the thing is that you're trying to do. Do the people this
> project is aimed at (and you've said there's fourty of them) have _any_
> idea about Perl/MySQL integration? If not, you're screwed.
Couple of years back, I have been introduced and worked on mysql but
for very limited time (~ 6 months with no formal training) as part of
requirement to develop web based application / tools. Though, I
remember (very vaguely) some of the concepts but need to refresh the
basics and those parts that will be needed for the current assignment.
> Umm, because generally CGIs suck? What happens is that the interpreter
> (for whatever language the CGI is written in; in this case Perl) is
> spawned for every instance the page is viewed. Hence you can quickly
> see how slow and cumbersome it would get for a multi-user environment.
> Not to mention that persistent states would be compromised. At least if
> it is via mod_perl, it's Apache which spawns the process. This means
> that only one instance need be created for all instances it is viewed at
> if it is concurrent.
That sounds like, mod_perl is the way to go.
> Then there you go. ;) Again, until you provide more details, I can't
> help you. Note that my day job is perl programming with CGIs, so make
> use of this resource. :P
I have written / come up with basic script (very very primitive to say
the least) which I would like to share with you.
It was heartening to note that you are willing to extend your guidance
in this regd. Thanks very much.
Hence, am considering to take your help / mentoring in this project
(personally, I would like to make this happen, even if I do not have
the chance to setup this project at my workplace, it will give me
needed exp with web-based appln development), if you are willing.
More information about the TAG