Torsten Neuer (email@example.com)
Tue, 1 Jun 1999 18:59:11 +0200
According to Mark Foster:
>Servlets are more efficient than CGI, because a separate process does not
>have to be spawned for each request.
This is true, but not for all cases. It is limited to those cases where
the overhead of starting up the CGI process is not recovered by a faster
execution of the application requested.
Servlets are *interpreted* (even though they might be byte-compiled) which
makes them quite inefficient in general. Any CGI written in Ada, C, C++
or other languages which are compiled into native code of the hosting server
will outperform a servlet in all cases where the execution speed makes up
for the additional load time. And this is true for most applications that
go beyond a web-counter or a simple FORMs handler.
However, it is more often a matter of taste and even if the method chosen
is slower might pay off with regards to site maintenance. This depends upon
what people are working at the site and what kind of software is used there
in general. Btw are there many methods of reducing the overhead of Perl based
CGI (like Apache's mod_perl).
-- InWise - Wirtschaftlich-Wissenschaftlicher Internet Service GmbH Waldhofstraße 14 Tel: +49-4101-403605 D-25474 Ellerbek Fax: +49-4101-403606 E-Mail: firstname.lastname@example.org Internet: http://www.inwise.de
------------------------------------ To unsubscribe from the htdig mailing list, send a message to email@example.com containing the single word "unsubscribe" in the SUBJECT of the message.
This archive was generated by hypermail 2.0b3 on Tue Jun 01 1999 - 09:30:51 PDT