Servlets are more scalable than CGIs and that is what is one of the biggest advantages!
A Servlet is instantiated for the first request and any subsequent requests to the same servlet spawns a separate thread, whereas CGIs are costly and had to be instantiated afresh for every fresh request. This way CGIs are more prone to bottlenecks and timeouts than Servlets. -- Rex > -----Original Message----- > From: Brett W. McCoy [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 08, 2002 4:51 PM > To: Naveen Parmar > Cc: [EMAIL PROTECTED] > Subject: Re: CGI vs. Servlet technologies > > > On Tue, 8 Jan 2002, Naveen Parmar wrote: > > > What are the key differences between CGI and Servlets? > > I think Servlets also use the CGI protocol, they accept POST and GET > strings the same way as any CGI program. They are just special server > side components written in Java that are run as a server process via a > 'servlet' container, like Tomcat. Some servlet containers can run > standalone as a web server (Tomcat can), others, need to be run as a > process invoked by a web server like Apache via an > intermediary module, > like mod_jk. Actually, Tomcat can be used as either of these. :-) Of > course, Servlets are specifically Java, CGI is a broader > category that can > be implemented in any language. > > Servlets are closer in principle to things like mod_perl, > which embeds a > Perl interpreter into the web server. JSP, Java Server Pages, get > converted and then compiled into servlets in a manner very > similar to the > way Mason converts components into compilable Perl code. > > -- Brett > > http://www.chapelperilous.net/ > -------------------------------------------------------------- > ---------- > Kramer's Law: > You can never tell which way the train went by looking > at the tracks. > > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >