Package org.eodisp.remote.jeri.jxta

Provides implementations of the Endpoint and ServerEndpoint abstractions that use JXTA sockets as the underlying communication mechanism.

See:
Description

Class Summary

Constraints	Copied from net.jini.jeri.tcp.Constraints.
Constraints.Distilled	A distillation of constraints to a form more directly usable by this provider.
JxtaEndpoint	An implementation of the Endpoint abstraction that uses JXTA sockets (instances of JxtaSocket) for the underlying communication mechanism.
JxtaNetwork	Static configuration of the JXTA transport layer for Jeri.
JxtaServerEndpoint	An implementation of the ServerEndpoint abstraction that uses JXTA sockets (instances of JxtaServerSocket) for the underlying communication mechanism.

Package org.eodisp.remote.jeri.jxta Description

Provides implementations of the Endpoint and ServerEndpoint abstractions that use JXTA sockets as the underlying communication mechanism. Requests and responses are framed and multiplexed over socket connections using the Jini(TM) extensible remote invocation (Jini ERI) multiplexing protocol.

A net.jini.jeri.tcp.JxtaEndpoint can be used to initiate requests over JXTA. Each instance contains a peer id. When initiating a new request, a new socket connection is created to the peer id, if an existing connection is not already available for use.

A net.jini.jeri.tcp.JxtaServerEndpoint can be used to listen for and receive incoming requests over a JXTA socket connection.

Jini ERI multiplexing protocol mapping

JxtaEndpoint and JxtaServerEndpoint map, respectively, OutboundRequest and InboundRequest instances to distinct sessions of a Jini ERI multiplexing protocol connection. For each new request initiated, a JxtaEndpoint starts a new session as the client of a connection to the remote endpoint. As the server of an accepted connection, a JxtaServerEndpoint creates a new InboundRequest to represent each session started by the remote endpoint. Request data is transmitted as the data sent for the corresponding session by the client, and response data is transmitted as the data sent for the corresponding session by the server. Jxta socket connections are reused by a JxtaEndpoint when possible. This implementation uses ConnectionManager and ServerConnectionManager for connection management.

Logging

This implementation uses the Logger named net.jini.jeri.jxta.client to log information at the following levels:

Level	Description
FAILED	exceptions thrown attempting to initiate a request
HANDLED	exceptions caught attempting to connect a socket, set options on a client-side socket, or reuse a connection
FINE	client-side socket operations (create, connect, reuse, and close)

This implementation uses the Logger named net.jini.jeri.jxta.server to log information at the following levels:

Level	Description
WARNING	exceptions accepting on a server socket
HANDLED	exceptions caught setting options on a server-side socket
FINE	server-side socket operations (create, accept, and close)