| IBM WebSphere Extended Deployment (XD)TM
Release 6.0 |
Method Summary | |
---|---|
public
InetAddress | getClientAddr()
Returns the Internet Protocol (IP) address of the client that sent the flow.
|
public
int | getClientPort()
Returns the port number of the client that sent the flow.
|
public
InetAddress | getLocalAddr()
Returns the Internet Protocol (IP) address of the proxy server that received the request.
|
public
int | getLocalPort()
Returns the proxy server port number that received the request. For HTTP, this means the .
|
public
boolean | resume()
Resumes processing of this service context after a filter suspended its
processing by returning a wait status code.
|
public
boolean | resume(com.ibm.wsspi.filter.DispatchMode)
Resumes processing of this service context after a filter suspended its processing by returning a wait status code..
|
Methods inherited from com.ibm.wsspi.proxy.filter.FilterAttributeBucket |
---|
containsAttribute, getAttribute, getAttributes, removeAttribute, setAttribute |
Method Detail |
public InetAddress getClientAddr( | ) |
InetAddress
containing the IP address of the client that sent the flow.
public int getClientPort( | ) |
public InetAddress getLocalAddr( | ) |
InetAddress
containing the IP address of the server that received the flow.
public int getLocalPort( | ) |
Host
header, if any, or the proxy server port
upon which the client connection was accepted.
public boolean resume( | ) |
All protocols do not support wait status codes. This method is effectively a no-op for those protocols and filters that do not support waiting.
Refer to #resume(DispatchMode dispatchMode) for further details.
public boolean resume( | DispatchMode dispatchMode )
|
All protocols do not support wait status codes. This method is effectively a no-op for those protocols and filters that do not support waiting.
dispatchMode
-
Determines the thread dispatch behavior when resuming the service context.
=DispatchMode.CURRENT_THREAD
, the service context will be immediately resumed
on the current thread.
=DispatchMode.ANOTHER_THREAD
, the service context will be resumed on another thread
upon successful dispatch. Upon failure to dispatch, the service context will be resumed on the current thread.
=DispatchMode.DISCARD_ON_ERROR
, the service context will be resumed on another thread upon
successful dispatch. Upon failure to dispatch, the service context will be discarded and no further
execution of the service context will occur.
=DispatchMode.DispatchMode.ANOTHER_THREAD_EXPAND
resume execution on another thread upon succesful dispatch.
If the request queue is full at the time of initial dispatch, it will be expanded and the service context will be dispatched
to resume execution. If the expanded request buffer becomes full, execution will resume on the current thread.
=DispatchMode.DispatchMode.ANOTHER_THREAD_EXPAND_DISCARD
Resume execution on another thread upon succesful dispatch.
If the request queue is full at the time of initial dispatch, it will be expanded and the service context will be dispatched
to resume execution. If the expanded request buffer becomes full, the service context will be discarded and execution will not
resume.
| IBM WebSphere Extended Deployment (XD)TM
Release 6.0 |