All Known Implementing Classes:
LoggingIOSession, IOSessionImpl, SSLIOSession
The channel associated with implementations of this interface can be used to read data from and write data to the session.
I/O sessions are not bound to an execution thread, therefore one cannot use the context of the thread to store a session's state. All details about a particular session must be stored within the session itself, usually using execution context associated with it.
Implementations of this interface are expected to be threading safe.
$ - Revision: 744545 $4.0 - | Field Summary | ||
|---|---|---|
| public static final String | ATTACHMENT_KEY | Name of the context attribute key, which can be used to obtain the session attachment object. |
| public static final int | ACTIVE | |
| public static final int | CLOSING | |
| public static final int | CLOSED | |
| Method from org.apache.http.nio.reactor.IOSession Summary: |
|---|
| channel, clearEvent, close, getAttribute, getEventMask, getLocalAddress, getRemoteAddress, getSocketTimeout, getStatus, hasBufferedInput, hasBufferedOutput, isClosed, removeAttribute, setAttribute, setBufferStatus, setEvent, setEventMask, setSocketTimeout, shutdown |
| Method from org.apache.http.nio.reactor.IOSession Detail: |
|---|
|
|
|
null if not set.
The value of the session attachment object can be obtained using #ATTACHMENT_KEY name. |
|
|
|
0 signifies the session cannot time out. |
|
|
|
|
|
I/O sessions are not bound to an execution thread, therefore one cannot use the context of the thread to store a session's state. All details about a particular session must be stored within the session itself. |
I/O sessions can be made aware of the status of external session buffers using the SessionBufferStatus interface. |
|
|
0 signifies the session cannot time out. |
|