CGI typically starts a new executable --meaning it creates a new process.
That is very time consuming.
Servlet after they are loaded for the first time, are living in the
process space already created by the server.
So to start a execution of already loaded code is much faster.
-rrs
----- Original Message -----
From: maurice munoz <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 29, 1999 11:52 AM
Subject: cgi vs serv
> newbie question?
> How fast is CGI(perl) compared to Servlets.
> How is that determined.?
>
>
> ----- Original Message -----
> From: Jason Hunter <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, April 29, 1999 2:40 PM
> Subject: Re: JSDK 2.1 path specs
>
>
> > > The readme says that the servlets are located in
> > > /examples/web-inf/servlets
> > >
> > > How could I deduce (and thus change) this by reading default.cfg or
> > > any of the properties files?
> > > In other words, how do I tell a configuration file where to look for
> > > my servlet?
> >
> > Servlets are either in context/path/WEB-INF/servlets (where they're by
> > default accessed as /context/path/servlet/Foo) or they're in the
> > server's classpath. If you look, the classpath set by the startup
> > script includes jsdk2.1/classes, but you can change that within the
> > startup script.
> >
> > In default.cfg you can see how contexts are added. Contexts can be
> > dirs or even other sites. How's this one for cool:
> >
> > server.app.proxy.mapping=/proxy
> > server.app.proxy.base=http://otherserver/
> >
> > Now http://localhost:8080/proxy/index.html serves
> > http://otherserver/index.html. Fun, cool, and even potentially useful
> > when you have a client with limited network visibility.
> >
> > I think the API 2.1 getResource() abstraction facilitated this.
> > For more fun, picture if you write a new protocol handler what you
> > could do here.
> >
> > server.app.db.mapping=/db
> > server.app.db.base=dbtp://something
> >
> > Assuming you wrote a protocol handler for the "database transfer
> > protocol", you could as easy as this serve files coming from a db.
> > Exactly how URIs mapped to db queries would be known by the dbtp
> > handler.
> >
> > -jh-
> >
> > --
> > Jason Hunter
> > [EMAIL PROTECTED]
> > Book: http://www.servlets.com/book
> > Article: http://www.javaworld.com/jw-12-1998/jw-12-servletapi.html
> >
> >
>
___________________________________________________________________________
> > 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
>
>
___________________________________________________________________________
> 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
___________________________________________________________________________
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
