See: Description
| Interface | Description |
|---|---|
| VmPipeSessionConfig |
An
IoSessionConfig for vmpipe transport type. |
| Class | Description |
|---|---|
| DefaultVmPipeSessionConfig |
A default implementation of
VmPipeSessionConfig. |
| VmPipe |
TODO Add documentation
|
| VmPipeAcceptor |
Binds the specified
IoHandler to the specified
VmPipeAddress. |
| VmPipeAddress |
A
SocketAddress which represents in-VM pipe port number. |
| VmPipeConnector |
Connects to
IoHandlers which is bound on the specified
VmPipeAddress. |
| VmPipeConnector.LocalAddressReclaimer | |
| VmPipeFilterChain |
TODO Add documentation
|
| VmPipeSession |
A
IoSession for in-VM transport (VM_PIPE). |
In-VM pipe is a direct event forwarding mechanism between two
ProtocolHandlers in the
same Java Virtual Machine. Using in-VM pipe, you can remove the overhead
of encoding and decoding which is caused uselessly by local loopback
network communication. Here are some useful situations possible:
Please refer to Tennis example.