Michael,
My aim is to create a website using Perl for dynamically creating
the webpages. But I don't want to use CGI, because I read that since CGI
create a seperate connection for every user, it thereby uses more memory,
than say an ASP application.
I don't mind using CGI, but if there are other options available,
then I want to look thru them also.
George Savio Pereira
^^^^^^^^^^^^^^^^^^^^
Email : [EMAIL PROTECTED]
On Wed, 11 Jul 2001, Michael Fowler wrote:
> On Wed, Jul 11, 2001 at 01:52:58PM +0530, George S Pereira wrote:
> > Using CGI as a bridge between Perl and the Internet has some
> > disadvantages, prominent is the increased use of memory.
>
> I'm not sure how you can say one of CGI's disadvantages is increased use of
> memory when you aren't comparing it to anything.
>
> Also, let's be very clear; CGI is not a bridge between Perl and the
> Internet, it's a protocol between a web server and an application. There
> are many things wrong with saying it's a "bridge between Perl and the
> Internet", not the least of which is the fact that CGI is used only in one
> domain, the web. Granted, this is a fairly visible domain, but it is not
> the whole of the internet.
>
>
> > Is there another alternative for connecting Perl with the Internet
> > other than CGI ???? (Like maybe using Perl with ASP!!!)
>
> There are other ways of dynamically generating web content with Perl. With
> the Apache web server the primary (possibly only, I can't think of any
> others) alternative is mod_perl. With mod_perl you setup hooks inside the
> web server for authenticating users, generating content, and various other
> things.
>
> This is all very generic and academic, though. What is your overall goal?
>
>
> Michael
> --
> Administrator www.shoebox.net
> Programmer, System Administrator www.gallanttech.com
> --
>
>
