Represent a response context that is passed by thread local using
determines ther behaviour of sending a callback to the client.
Base class for response context implementations
A Channel Entry is an entry in the Pivot Channels Table.
Holds cpeer watched objects At any given moment, at most 1 object is being watched.
CPeer is the LRMI over NIO Client Peer.
The default behavior that actually sends the response to the client.
This class provides full information about physical connection to the remote object.
An NIO based implementation of LRMI Protocol Adapter The basic design is as follows: There will be a single 'pivot' object at the server side, that will act as a local proxy for all server peers in the server JVM.
The Pivot is the center of the NIO Protocol Adapter server-side implementation.
A Reader is capable of reading Request Packets and Reply Packets from a Socket Channel.
A thread local class that keeps the context of the remote class loader
A Reply Packet is constructed by the NIO server and sent back to the client peer.
A Request Packet is constructed by the NIO client peer and sent to the server.
This is a thread local based context that is used to send response back to the client not in the current stack, but rather from a different thread that will use a stored context in the memory.
SPeer is the LRMI over NIO Server Peer.
Created by IntelliJ IDEA.
A Writer is capable of writing Request Packets and Reply Packets to a Socket Channel.
a runtime exception that indicate a problem in serialization of user objects before sending it over the wire.
thrown whenever an IOException is thrown during the unmarshalling process of request/response from the wire.
Copyright © GigaSpaces.