See: Description
| Interface | Description |
|---|---|
| Connection |
Represents an established client-side connection.
|
| ConnectionEndpoint |
Represents a remote communication endpoint to establish connections
to.
|
| InboundRequestHandle |
Associates information with a request that is being received on a
ServerConnection. |
| OutboundRequestHandle |
Associates information with a request that is being sent to a
ConnectionEndpoint. |
| ServerConnection |
Represents an established server-side connection.
|
| Class | Description |
|---|---|
| ConnectionManager |
Provides client-side connection management using the Jini extensible
remote invocation (Jini ERI) multiplexing protocol
to frame and multiplex requests and responses over connections.
|
| ServerConnectionManager |
Provides server-side connection management using the Jini
extensible remote invocation (Jini ERI) multiplexing protocol
to frame and multiplex requests and responses over connections.
|
With the implementation model of this package, a connection-based
transport implementation only needs to provide access to established
connections, via byte streams or (optionally) socket channels (see
SocketChannel), to connection managers; the
connection managers then take care of implementing the Jini ERI
client-side and server-side request/response interfaces (OutboundRequestIterator, OutboundRequest, and InboundRequest) on top of those connections.
Specifically, the client side of a connection-based transport
implementation provides implementations of the ConnectionEndpoint, Connection, and OutboundRequestHandle interfaces, and the
server side provides implementations of the ServerConnection and InboundRequestHandle interfaces.
ConnectionManager and ServerConnectionManager provide client-side
and server-side connection management using the Jini extensible remote invocation (Jini
ERI) multiplexing protocol.
Copyright 2007-2013, multiple authors.
Licensed under the Apache License, Version 2.0, see the NOTICE file for attributions.