| org.apache.tomcat.util.net.TcpConnectionHandler
All known Subclasses: org.apache.ajp.tomcat33.Ajp14Interceptor,
| TcpConnectionHandler | | public interface TcpConnectionHandler (Code) | | This interface will be implemented by any object that
uses TcpConnections. It is supported by the pool tcp
connection manager and should be supported by future
managers.
The goal is to decouple the connection handler from
the thread, socket and pooling complexity.
|
| Method Summary | |
| public Object[] | init()
Called before the call to processConnection. | | public void | processConnection(TcpConnection connection, Object thData)
Assert: connection!=null
Assert: connection.getSocket() != null
Assert: thData != null and is the result of calling init()
Assert: thData is preserved per Thread. | | public void | setAttribute(String name, Object value)
| | public void | setServer(Object manager)
Add informations about the a "controler" object
specific to the server. |
| init | | public Object[] init()(Code) | | Called before the call to processConnection.
If the thread is reused, init() should be called once per thread.
It may look strange, but it's a _very_ good way to avoid synchronized
methods and keep per thread data.
Assert: the object returned from init() will be passed to
all processConnection() methods happening in the same thread.
|
| processConnection | | public void processConnection(TcpConnection connection, Object thData)(Code) | | Assert: connection!=null
Assert: connection.getSocket() != null
Assert: thData != null and is the result of calling init()
Assert: thData is preserved per Thread.
|
| setAttribute | | public void setAttribute(String name, Object value)(Code) | | Used to pass config informations to the handler
This has nothing to do with Tcp,
was used as a workaround
|
| setServer | | public void setServer(Object manager)(Code) | | Add informations about the a "controler" object
specific to the server. In tomcat it will be a
ContextManager.
|
|
|