Allows to use different annotation based injection and configuration associated with remoting.
The remoting service exporter holds a list of services that can be exported for remoting operations
using the Space as the transport layer. The exporter is a SpaceDataEventListener and should be plugged
with a polling container to enable async (communication) remoting. It is also a Space filter which can
be plugged to be used with sync (communication) remoting.
The services must implement one or more interfaces which are then used as the key to look them up.
Allows to set a aspect around each service execution.
".]]>
A service that will be exposed as a remoting services with the Space as the
transport layer. Must implement one or more interfaces.
".]]>
Allows to narrow down the async polling container to perform a lookup only on specific
lookup name (which is usually the interface that will be used to proxy it on the client
side). Defaults to match on all async remoting invocations. This option allows to create
several polling container, each for different service that will perform the actual
invocation.
A space even driven remoting proxy that forward the service execution to a remote service with the space as
the transport layer. Services are remotely exported in the "server side" using the 'service-exporter'
(using a polling container).
Event driven remoting refers to the communication protocol between the proxy and the service exporter. Even driven
uses a command entry written to the Space representing a remote invocation. On the "server side" the
service exporter waits for the remote invocation using an event container, invokes the proper matching service, and writes the
result back to the Space. The even driven proxy in the meanwhile waits for the response (when returning non
Future) or returns a Future.
In case of remote invocation over a partitioned space the default partitioned
routing index will be random (the hashCode of the newly created remote invocation).
This RemoteRoutingHandler allows for custom routing computation (for example, based
on one of the service method parameters).
".]]>
Allows to set the meta arguments handler controlling the meta arguments passed with
each remote invocation.
".]]>
".]]>
Sets the GigaSpace interface that will be used to work with the space as the transport
layer for both writing and taking EventDrivenSpaceRemotingEntry.
The interface (fully qualified class name) that this remoting proxy will proxy. Also
controls which service will be invoked in the "server".
If set to true (defaults to false) service methods that return void will be invoked and
the proxy will not wait for a return value. Note, any exception raised by the remote
service will be logged on the server side and not propagated to the client.
If set to true (defaults to false) all of the service methods will be invoked and the
proxy will not wait for a return value. Note, any exception raised by the remote service
will be logged on the server side and not propagated to the client.
Sets the timeout that will be used to wait for the remote invocation response. The
timeout value is in milliseconds and defaults to 60000 (60 seconds).
Sets the remote invocation objects written to the Space to work in FIFO. Note, when
setting this setting make sure to set it on the 'service-exporter'. This allows for
remoting to work in fifo mode without needing to set the whole Space to work in fifo
mode.
In case of remote invocation over a partitioned space the default partitioned
routing index will be random (the hashCode of the newly created remote invocation).
This RemoteRoutingHandler allows for custom routing computation (for example, based
on one of the service method parameters).
".]]>
When using broadcast set to true, allows to plug a custom reducer that can reduce
the array of result objects into another response object.
".]]>
Allows to set the meta arguemnts handler controlling the meta arguments passed with
each remote invocation.
".]]>
".]]>
Sets the GigaSpace interface that will be used to work with the space as the transport
layer for executions of Space tasks.
The interface (fully qualified class name) that this remoting proxy will proxy. Also
controls which service will be invoked in the "server".
Sets the timeout that will be used to wait for the remote invocation response. The
timeout value is in milliseconds and defaults to 60000 (60 seconds).
If set the true (defaults to false) causes the remote invocation to be called on all
active (primary) cluster members.
When set to true (defaults to true) will return the first result when using broadcast.
If set to false, an array of results will be retuned. Note, this only applies when
not setting a reducer.