CGI has a lot of drawbacks of course but one nice thing about CGI from an
ISP's perspective is that when only a few users are using a server at a time
then only a few resources are in use at that time, no need to run any kind
of daemons or VMs are anything like that. Also, process separation from
the web server and from other users is nice, and OS enforced security by
running the processes under the user's ID(optional). All this lets an ISP
host many lightly used domains on a single machine in a reliable way. A
CGI-like approach to providing services would be could for any shared
server. Better performance than CGI is desirable. Heavily used domains
will get their own dedicated machines and use servlet engines whose design
puts emphasis on speed.
> -----Original Message-----
> From: Robb Shecter [SMTP:[EMAIL PROTECTED]]
> Ted Stockwell wrote:
> > I think this scenario combines the benefits of CGI with the benefits of
> Java
> > servlets.
>
> Hi,
>
> No joke, here, but -what- benefits of CGI? I can only think of
> disadvantages
> of the hack^h^h^h system.
>
>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
