What is a Servlet Container?
The servlet container is a part of aWeb server or application server that provides the network services over which requests and responses are sent, decodes MIME-based requests, and formats MIME-based responses. A servlet container also contains and manages servlets through their lifecycle.
A servlet container can be built into a host Web server, or installed as an addon component to a Web Server via that server’s native extension API. Servlet containers can also be built into or possibly installed into Web-enabled application servers.
All servlet containers must support HTTP as a protocol for requests and responses, but additional request/response-based protocols such as HTTPS (HTTP over SSL) may be supported. The required versions of the HTTP specification that a container must implement are HTTP/1.0 and HTTP/1.1. Because the container may have a caching mechanism described in RFC2616(HTTP/1.1), it may modify requests from the clients before delivering them to the servlet, may modify responses produced by servlets before sending them to the clients, or may respond to requests without delivering them to the servlet under the compliance with RFC2616.
A servlet container may place security restrictions on the environment in which a servlet executes. In a Java 2 Platform, Standard Edition (J2SETM, v.1.3 or above) or Java 2 Platform, Enterprise Edition (J2EETM, v.1.3 or above) environment, these restrictions should be placed using the permission architecture defined
by the Java 2 platform. For example, high-end application servers may limit the creation of a Thread object to insure that other components of the container are not negatively impacted.
J2SE 1.3 is the minimum version of the underlying Java platform with which servlet containers must be built.
A servlet container can be built into a host Web server, or installed as an addon component to a Web Server via that server’s native extension API. Servlet containers can also be built into or possibly installed into Web-enabled application servers.
All servlet containers must support HTTP as a protocol for requests and responses, but additional request/response-based protocols such as HTTPS (HTTP over SSL) may be supported. The required versions of the HTTP specification that a container must implement are HTTP/1.0 and HTTP/1.1. Because the container may have a caching mechanism described in RFC2616(HTTP/1.1), it may modify requests from the clients before delivering them to the servlet, may modify responses produced by servlets before sending them to the clients, or may respond to requests without delivering them to the servlet under the compliance with RFC2616.
A servlet container may place security restrictions on the environment in which a servlet executes. In a Java 2 Platform, Standard Edition (J2SETM, v.1.3 or above) or Java 2 Platform, Enterprise Edition (J2EETM, v.1.3 or above) environment, these restrictions should be placed using the permission architecture defined
by the Java 2 platform. For example, high-end application servers may limit the creation of a Thread object to insure that other components of the container are not negatively impacted.
J2SE 1.3 is the minimum version of the underlying Java platform with which servlet containers must be built.
No comments:
Post a Comment