servlet的生命周期（The life cycle of Servlet）.docVIP

servlet的生命周期（The life cycle of Servlet） Although you can use JSP objects with Servlet, you cant plug them into HTML like javaBean -- So, Tag (label) appeared (you can use all the JSP implicit objects), it completely solved the problem, so you can write a pure HTML JSP the benefits of natural self-evident: higher maintainability and reuse more efficient, more easily the maintenance of HTML page Servlet profile Servlet container: Handle customer requests, send requests to servlet and return results to customers. The actual implementation of different container program may vary, but between the container and the servlet interface is defined by servletAPI, this interface defines the method call on the servlet to the servlet container and the object passed to servlet. The life cycle of servlet: The L servlet container creates an instance of Servlet The L container calls the init () method of the instance L if the container has a request to the servlet, call the service () method of this instance The L container calls its destroy () method before destroying the instance L destroys and tags the instance for garbage collection Once a servlet is requested, there is no way to prevent the container from executing a full lifecycle. The container creates an instance of servlet when it is called first, and keeps the instance in memory, allowing it to process all requests. The container may decide to remove the instance from memory at any time. In the typical model, the container creates a separate instance for each servlet, each container is not received a request to create a new thread, but the use of a dynamic thread pool to the thread assigned to incoming requests, but from the perspective of the servlet effect, and create a request the effect is the same for each new thread. Servlet API Servlet interface: Public interface Servlet Its lifecycle is defined by the javax.servlet.servlet interface. When you write servlet, you must implement this interface directly or indirectly.