Uses of Package
com.gigaspaces.lrmi.nio
Packages that use com.gigaspaces.lrmi.nio
Package
Description
Provides GigaSpaces LRMI (Light-RMI) package.
Provides classes to configure and customize IO Filters (e.g.
Provides GigaSpaces client interface services
-
Classes in com.gigaspaces.lrmi.nio used by com.gigaspaces.events.batching
-
Classes in com.gigaspaces.lrmi.nio used by com.gigaspaces.internal.client.spaceproxy.operations
-
Classes in com.gigaspaces.lrmi.nio used by com.gigaspaces.internal.lrmiClassDescriptionA Channel Entry is an entry in the Pivot Channels Table.A Reader is capable of reading Request Packets and Reply Packets from a Socket Channel.A Writer is capable of writing Request Packets and Reply Packets to a Socket Channel.
-
Classes in com.gigaspaces.lrmi.nio used by com.gigaspaces.internal.remoting
-
Classes in com.gigaspaces.lrmi.nio used by com.gigaspaces.internal.remoting.routing.partitioned
-
Classes in com.gigaspaces.lrmi.nio used by com.gigaspaces.internal.server.storageClassDescriptionRepresent a response context that is passed by thread local using
ResponseContextfor callback invocations -
Classes in com.gigaspaces.lrmi.nio used by com.gigaspaces.lrmiClassDescriptionAn 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.
-
Classes in com.gigaspaces.lrmi.nio used by com.gigaspaces.lrmi.classloading
-
Classes in com.gigaspaces.lrmi.nio used by com.gigaspaces.lrmi.nioClassDescriptionBase class for response context implementationsA Channel Entry is an entry in the Pivot Channels Table.CPeer is the LRMI over NIO Client Peer.Similar to
Externalizablebut expectsMarshalOutputStreamRepresent a response context that is passed by thread local usingResponseContextfor callback invocationsdetermines ther behaviour of sending a callback to the client.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 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.A Writer is capable of writing Request Packets and Reply Packets to a Socket Channel. -
Classes in com.gigaspaces.lrmi.nio used by com.gigaspaces.lrmi.nio.asyncClassDescriptionHolds cpeer watched objects At any given moment, at most 1 object is being watched.CPeer is the LRMI over NIO Client Peer.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.
-
Classes in com.gigaspaces.lrmi.nio used by com.gigaspaces.lrmi.nio.filtersClassDescriptionA Reader is capable of reading Request Packets and Reply Packets from a Socket Channel.A Writer is capable of writing Request Packets and Reply Packets to a Socket Channel.
-
Classes in com.gigaspaces.lrmi.nio used by com.gigaspaces.lrmi.nio.selectorClassDescriptionThe Pivot is the center of the NIO Protocol Adapter server-side implementation.
-
Classes in com.gigaspaces.lrmi.nio used by com.gigaspaces.lrmi.nio.selector.handlerClassDescriptionA Channel Entry is an entry in the Pivot Channels Table.The Pivot is the center of the NIO Protocol Adapter server-side implementation.
-
Classes in com.gigaspaces.lrmi.nio used by com.gigaspaces.lrmi.nio.selector.handler.clientClassDescriptionA Request Packet is constructed by the NIO client peer and sent to the server.
-
Classes in com.gigaspaces.lrmi.nio used by com.j_spaces.core.client
-
Classes in com.gigaspaces.lrmi.nio used by com.j_spaces.core.server.processorClassDescriptionRepresent a response context that is passed by thread local using
ResponseContextfor callback invocationsA Reply Packet is constructed by the NIO server and sent back to the client peer.