public class RPCServer
The class RPCServer
implements the complement of RPCClient. When an RPC request arrives it dispatches to the
corresponding function in ops. During serialisation of the reply (and later observations) the server subscribes to
each Observable it encounters and captures the client address to associate with these Observables. Later it uses this
address to forward observations arriving on the Observables.
The way this is done is similar to that in RPCClient, we use Kryo and add a context to stores the subscription map.
class RPCServer
,
RPCClient,
RPCClientModifier and Type | Field and Description |
---|---|
static net.corda.node.services.messaging.RPCServer.Companion |
Companion |
Constructor and Description |
---|
RPCServer(RPCOps ops,
java.lang.String rpcServerUsername,
java.lang.String rpcServerPassword,
org.apache.activemq.artemis.api.core.client.ServerLocator serverLocator,
RPCUserService userService,
org.bouncycastle.asn1.x500.X500Name nodeLegalName,
RPCServerConfiguration rpcConfiguration)
The
class RPCServer implements the complement of RPCClient. When an RPC request arrives it dispatches to the
corresponding function in ops. During serialisation of the reply (and later observations) the server subscribes to
each Observable it encounters and captures the client address to associate with these Observables. Later it uses this
address to forward observations arriving on the Observables. |
Modifier and Type | Method and Description |
---|---|
void |
close() |
void |
start(org.apache.activemq.artemis.api.core.management.ActiveMQServerControl activeMqServerControl) |
public static net.corda.node.services.messaging.RPCServer.Companion Companion
public RPCServer(RPCOps ops, java.lang.String rpcServerUsername, java.lang.String rpcServerPassword, org.apache.activemq.artemis.api.core.client.ServerLocator serverLocator, RPCUserService userService, org.bouncycastle.asn1.x500.X500Name nodeLegalName, RPCServerConfiguration rpcConfiguration)
The class RPCServer
implements the complement of RPCClient. When an RPC request arrives it dispatches to the
corresponding function in ops. During serialisation of the reply (and later observations) the server subscribes to
each Observable it encounters and captures the client address to associate with these Observables. Later it uses this
address to forward observations arriving on the Observables.
The way this is done is similar to that in RPCClient, we use Kryo and add a context to stores the subscription map.
class RPCServer
,
RPCClient,
RPCClient