Home >> All >> org >> enhydra >> servlet >> [ connectionMethods Javadoc ]

•	org.enhydra.servlet.connectionMethods.EnhydraDirector.* (12)	•	org.enhydra.servlet.connectionMethods.http.* (11)
•	org.enhydra.servlet.connectionMethods.https.* (11)

• org.enhydra.servlet.connectionMethods: Javadoc index of package org.enhydra.servlet.connectionMethods.


Package Samples:

• org.enhydra.servlet.connectionMethods.EnhydraDirector
• org.enhydra.servlet.connectionMethods.http
• org.enhydra.servlet.connectionMethods.https

Classes:

• ConnectionMethod: A ConnectionMethod is how requests get into the server from the outside world. This interface defines the API an object must implement in order to be administered by the server. Each ConnectionMethod must maintain an ordered list of "channels". Each channel has an ID (a String), used to identify and refer to the channel. See addChannel() , below. Each channel can be enabled or disabled. When disabled, connections must be refused, and not passed on to any servlets. When enabled, connections are allowed through to the destination servlet. Each channel also contains an ordered list of TransactionFilters, ...
• EnhydraDirectorBufferedOutputStream: Extension of BufferedOutputStream to allow "reset" of the buffer. A servlet container's ServletResponse object should not go into the "committed" (data sent) state until the headers have actually been sent over the wire. This allows a servlet to specify a large buffer size and be able to reset or change headers well after the first byte of data has been written to the ServletOutputStream . This class has a reset() that, after checking for committed state of the connection, discards any buffered data and self destructs, dropping any reference to its internally held output stream. Once reset() has ...
• StandardConnectionMethod: This is a sample implementation of a ConnectionMethod. It is an abstract class because this class does not actually recieve or generate requests. It does do all the channel managment. Implementations of ConnectionMethod should extend this object, unless there is a specific reason not to. Classes that extend this class will need to implement the getChannelURL() and channelURLIsValid() functions. They will also need to ensure that they contain a thread that is started in the constructor or (prefered) initialize() , and stopped in destroy() .
• ConnectionMethodManager: This class maintains a set of ConnectionMethods. Each ConnectionMethod is associated with an identification string (symbolic name). This ID string is used to retrieve a ConnectionMethod. This class does not monitor the creation of ConnectionMethods. If you create one, you are responsible for adding it. These public methods are the only things that modify the set of ConnectionMethods managed by this class. (Note that this is different than the ServletManager, which is responsible for creating the Servlets it manages.)
• EnhydraDirectorConnectionMethod: The Enhydra connection method. Receives and handles requests using the Enhydra Protocol. The protocol is loosely based on the proposed Apache JServ 2.1 protocol, which uses a packet transmission scheme to allow a more rich set of communcation features between web servers and Enhydra. These features include: Round robin load balancing. Persistent connections. Connection Pools. Callbacks to the front-end web server.
• EnhydraDirectorInputStream: InputStream interface for the Enhydra connection method. Implemention of ServletInputStrem to be passed to servlets to allow them to receive the incoming HTTP request entity. This input stream and its underlying protocol receiver does not buffer input. Incoming entity bytes are read directly from the connected socket into the receiving buffer.
• EnhydraDirectorOutputStream: OutputStream interface for the Enhydra connection method. Implemention of ServletOutputStream to be passed to servlets to allow them to send response data to the client. This class automatically wrappers a lower level output stream in a BufferedOutputStream if buffering is requested by the servlet.
• EnhydraDirectorProtoOutputStream: The basic implementation of an output stream for EnhydraDirector. This implementation is intended to be used by the Enhydra connection method's EnhydraDirectorOutputStream class. If buffering is needed, this class can be wrappered in a BufferedOutputStream .
• HttpsRequestProcessor: Class that implements the request setup and parsing for HttpsRequest . This functionality is seperated into this class for organization purposes, with the internal functions being implemented here and the servlet interface being implemented in HttpsRequest .
• HttpRequestProcessor: Class that implements the request setup and parsing for HttpRequest . This functionality is seperated into this class for organization purposes, with the internal functions being implemented here and the servlet interface being implemented in HttpRequest .
• EnhydraDirectorFunction: Interface for pluggable EnhydraDirector protocol functions. EnhydraDirector function classes are only instantiated when their function number is requested for a particular connection. Each function is permanently hard-coded into a dispatch method in EnhydraDirectorProtocol.
• HttpHeaders: Class to store headers. This stores either a header or an array of headers, Depending if one or more instances of a header has been encountered. A hash table is not kept, as the order of writing headers seems to tickle bugs in certain browsers.
• HttpsHeaders: Class to store headers. This stores either a header or an array of headers, Depending if one or more instances of a header has been encountered. A hash table is not kept, as the order of writing headers seems to tickle bugs in certain browsers.
• ChannelStatus: ConnectionMethods return this object, which describes the current status of a channel in a ConnectionMethod. Do not modify the contents of this structure. Only ConnectionMethods should create instances of this object.
• HttpOutputStream: Implementation of a ServletOutputStream for the HTTP connection method. This object is designed to be recycled for several independent requests. For speed; it uses an internal buffer instead of
• HttpsOutputStream: Implementation of a ServletOutputStream for the HTTP connection method. This object is designed to be recycled for several independent requests. For speed; it uses an internal buffer instead of
• EnhydraDirectorBadStateException: Exception to signal that an EnhydraDirector connection has gotten into an unexpeceted state, or that one of its public methods has been called while the connection is in an incorrect state.
• HttpInputStream: Implementation of a ServletInputStream for the HTTP connection method. This object is designed to be recycled for several independent requests.
• HttpsInputStream: Implementation of a ServletInputStream for the HTTP connection method. This object is designed to be recycled for several independent requests.
• ConnectionMethodException: ConnectionMethods throw this type of exception when there is an error. Most likely this is a wrapper around the original exception that caused the error.
• HttpConnectionMethod: This class implements the connection method used to accept request for servlets from an HTTP client.
• HttpsConnectionMethod: This class implements the connection method used to accept request for servlets from an HTTP client.
• EnhydraDirectorException: Exception to signal that an EnhydraDirector connection has encountered an error.
• EnhydraDirectorHandler: This class processes servlet requests from the EnhydraDirectorConnectionMethod.
• HttpResponse: Implementation of a HTTP servlet response for the HTTP connection method.

Home | Contact Us | Privacy Policy | Terms of Service