org.apache.tomcat.util.net

Interface TcpConnectionHandler

Known Implementing Classes:
Ajp14Interceptor

public interface TcpConnectionHandler

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

Object[]
init()
Called before the call to processConnection.
void
processConnection(TcpConnection connection, thData[] )
Assert: connection!=null Assert: connection.getSocket() != null Assert: thData != null and is the result of calling init() Assert: thData is preserved per Thread.
void
setAttribute(String name, Object value)
Used to pass config informations to the handler
void
setServer(Object manager)
Deprecated. This has nothing to do with TcpHandling, was used as a workaround

Method Details

init

public Object[] init()
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,
                              thData[] )
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)
Used to pass config informations to the handler


setServer

public void setServer(Object manager)

Deprecated. This has nothing to do with TcpHandling, was used as a workaround

Add informations about the a "controler" object specific to the server. In tomcat it will be a ContextManager.


Copyright B) 2000-2003 Apache Software Foundation. All Rights Reserved.