|Home >> All >> org >> apache >> [ coyote Javadoc ]|
|||org.apache.coyote.ajp.* (4)||||org.apache.coyote.http11.* (24)|
|||org.apache.coyote.http11.filters.* (9)||||org.apache.coyote.memory.* (1)|
|||org.apache.coyote.tomcat3.* (4)||||org.apache.coyote.tomcat4.* (13)|
org.apache.coyote: Javadoc index of package org.apache.coyote.
CoyoteInterceptor2: Standalone http. Connector properties: secure - will load a SSL socket factory and act as https server Properties passed to the net layer: timeout backlog address port Thread pool properties: minSpareThreads maxSpareThreads maxThreads poolOn Properties for HTTPS: keystore - certificates - default to ~/.keystore keypass - password clientauth - true if the server should authenticate the client using certs Properties for HTTP: reportedname - name of server sent back to browser (security purposes) compression - use gzip compression in HTTP 1.1 (on/off) - def off compressionMinSize - minimum size content ...
CoyoteServerSocketFactory: This socket factory holds secure socket factory parameters. Besides the usual configuration mechanism based on setting JavaBeans properties, this component may also be configured by passing a series of attributes set with calls to setAttribute() . The following attribute names are recognized, with default values in square brackets: algorithm - Certificate encoding algorithm to use. [SunX509] clientAuth - Require client authentication if set to true . Want client authentication if set to want . (Note: Only supported in the JSSE included with J2SDK 1.4 and above. Prior versions of JSSE and PureTLS ...
Request: This is a low-level, efficient representation of a server request. Most fields are GC-free, expensive operations are delayed until the user code needs the information. Processing is delegated to modules, using a hook mechanism. This class is not intended for user code - it is used internally by tomcat for processing the request in the most efficient way. Users ( servlets ) can access the information using a facade, which provides the high-level view of the request. For lazy evaluation, the request uses the getInfo() hook. The following ids are defined: req.encoding - returns the request encoding ...
RequestInfo: Structure holding the Request and Response objects. It also holds statistical informations about request processing and provide management informations about the requests beeing processed. Each thread uses a Request/Response pair that is recycled on each request. This object provides a place to collect global low-level statistics - without having to deal with synchronization ( since each thread will have it's own RequestProcessorMX ). TODO: Request notifications will be registered here.
ActionHook: Action hook. Actions represent the callback mechanism used by coyote servlet containers to request operations on the coyote connectors. Some standard actions are defined in ActionCode, however custom actions are permitted. The param object can be used to pass and return informations related with the action. This interface is typically implemented by ProtocolHandlers, and the param is usually a Request or Response object.
ProtocolHandler: Abstract the protocol implementation, including threading, etc. Processor is single threaded and specific to stream-based protocols, will not fit Jk protocols like JNI. This is the main interface to be implemented by a coyoute connector. Adapter is the main interface to be impleneted by a coyote servlet container.
AjpMessage: A single packet for communication between the web server and the container. Designed to be reused many times with no creation of garbage. Understands the format of data types for these packets. Can be used (somewhat confusingly) for both incoming and outgoing packets.
FileTester: File tester. This tester is initialized with an adapter (it will use the HTTP/1.1 processor), and will then accept an input file (which will contain the input data), and an output file, to which the result of the request(s) will be written.
ActionCode: Enumerated class containing the adapter event codes. Actions represent callbacks from the servlet container to the coyote connector. Actions are implemented by ProtocolHandler, using the ActionHook interface.
OutputBuffer: The buffer used by Tomcat response. This is a derivative of the Tomcat 3.3 OutputBuffer, with the removal of some of the state handling (which in Coyote is mostly the Processor's responsability).
Tomcat3Adapter: Adapter between Coyote and Tomcat. This class handles the task of passing of an individual request to Tomcat to handle. Also some of the connection-specific methods are delegated to here.
RequestGroupInfo: This can be moved to top level ( eventually with a better name ). It is currently used only as a JMX artifact, to agregate the data collected from each RequestProcessor thread.
AjpAprProtocol: Abstract the protocol implementation, including threading, etc. Processor is single threaded and specific to stream-based protocols, will not fit Jk protocols like JNI.
Http11Protocol: Abstract the protocol implementation, including threading, etc. Processor is single threaded and specific to stream-based protocols, will not fit Jk protocols like JNI.
Http11AprProtocol: Abstract the protocol implementation, including threading, etc. Processor is single threaded and specific to stream-based protocols, will not fit Jk protocols like JNI.
Http11BaseProtocol: Abstract the protocol implementation, including threading, etc. Processor is single threaded and specific to stream-based protocols, will not fit Jk protocols like JNI.
MemoryProtocolHandler: Abstract the protocol implementation, including threading, etc. Processor is single threaded and specific to stream-based protocols, will not fit Jk protocols like JNI.
Tomcat3Request: The Request to connect with Coyote. This class handles the I/O requirements and transferring the request line and Mime headers between Coyote and Tomcat.
InputBuffer: Input buffer. This class is used only in the protocol implementation. All reading from tomcat ( or adapter ) should be done using Request.doRead().
OutputBuffer: Output buffer. This class is used internally by the protocol implementation. All writes from higher level code should happen via Resonse.doWrite().
CoyotePrincipal: Generic implementation of java.security.Principal that is used to represent principals authenticated at the protocol handler level.
BufferedInputFilter: Input filter responsible for reading and buffering the request body, so that it does not interfere with client SSL handshake messages.
RandomAdapter: Adapter which will return random responses using pipelining, which means it will never try to generate bogus responses.
SavedRequestInputFilter: Input filter responsible for replaying the request body when restoring the saved request after FORM authentication.
VoidOutputFilter: Void output filter, which silently swallows bytes written. Used with a 204 status (no content) or a HEAD request.