In the school library, I saw "Java Servlet Programming" (O'Reilly), if she got treasure, borrowed, turned to renew, determined to take it well. Then there is the following learning notes.
This book has twenty-chapters, and the programming of servlet from the different aspects of the application of servlet is not a good book. In the note below, this twentieth chapter is summarized separately.
Java servlet? Vs cgi ================
CGI: Each CGI request creates a new process to run the CGI program, and the CGI program cannot interact with the server after running;
Java Servlet: It is a CGI solution, and Java servlets can run in different threads in the same process, or threads from different processes of multiple background servers. In operation, you can keep two-way communications with the server;
Java servlet support ============
* The API you need to support: ?? javax.servlet? And javax.servlet.http (already included in JDK)
* Requires servlet runner: Three popular: independent servlet containers, additional, and embedded;
Independent Servlet Container: is a server with a built-in support for servlet.
>> Apache Tomcat?: Sun Approved Servlet? Container
>> iPlanet (Netcape) Web Server Enterprise Edition may be the most popular server that provides built-in servlet support, this server is the fastest running servlet.
>> Caucho's Resin: Performance is good, can operate in separate mode, can be attached to other servers;
>> Zeus Web Server: It is considered the fastest server;
Application server
>> BEA WebLogic Application Server
>> IBM WebSphere Application Server
Additional servlet container
>> New Atlanta's servletexec
>> Aphace Tomcat
>> JRUN
There are still many advantages, such as portable, safe ...
