Apache::ASP might interest you, however, your'll still have your memory
problem as Mod_Perl stores within memory the servlet. Mod_perl is infamous
for using large amounts of ram, but hey, thats a GOOD thing in my book.
Better RAM then CPU/HDD
Machine code is still faster and less resource intensive, however production
time will grow like you've never seen before. We still use C++ for the
backend for BA.com. In my opinion you don't need this speed unless you get
millions of hits a month/day to a database driven system, and even then,
your hardware (RAID) needs to bee fast to keep up with the demand.
PHP uses less resources and is arguably quicker at this point in time. It is
designed for one job only, the web.
JSP is way to slow and its only plus is the wealth of JAVA developers out
there.
If you want power, modular support, speed, Mod_perl, and inparticular,
Apache::ASP is the current leader in my eyes.
Pierre
----- Original Message -----
From: "Aaron Craig" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 11, 2001 9:28 AM
Subject: Re: Is there an alternative to CGI ???
> You may be confusing your terms here. CGI (Common Gateway Interface) is a
> general term that is used to describe the various methods used to
> communicate between a host computer and a client through a network. There
> are many languages that can be used to handle this communication, such as
> Perl and even C++ (does anyone do that anymore?). However, if you're
> talking internet, you're talking CGI, no matter what you use to run your
> communication.
>
> At 13:52 11.07.2001 +0530, George S Pereira wrote:
>
> >Hi all,
> >
> > Using CGI as a bridge between Perl and the Internet has some
> >disadvantages, prominent is the increased use of memory.
> >
> > Is there another alternative for connecting Perl with the
Internet
> >other than CGI ???? (Like maybe using Perl with ASP!!!)
> >
> >
> >George Savio Pereira
> >^^^^^^^^^^^^^^^^^^^^
> >Email : [EMAIL PROTECTED]
>
> Aaron Craig
> Programming
> iSoftitler.com
