[EMAIL PROTECTED] wrote: > 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.
You'll find mod_perl will give you as much bang for your buck, if not more. Basically servlets and mod_perl are different ways of implementing persistence in web applications. A CGI application is an application stored on disk that is called by the web server every time a client hits the URI associated with it. A Servlet and a mod_perl handler are loaded from disk once (in most cases) and sit in memory waiting for each request. You can write a CGI app in anything, provided it prints out 'Content-type: text/html\n\n' before it prints anything else. Persistent technologies each have their own API and way of doing things. Visit http://perl.apache.org/guide for an intro to persistence/performance for Perl. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
