org.hyperledger.fabric.protos.gateway

Class GatewayGrpc.GatewayFutureStub

java.lang.Object

io.grpc.stub.AbstractStub<S>

io.grpc.stub.AbstractFutureStub<GatewayGrpc.GatewayFutureStub>

org.hyperledger.fabric.protos.gateway.GatewayGrpc.GatewayFutureStub

Enclosing class:

GatewayGrpc

public static final class GatewayGrpc.GatewayFutureStub
extends io.grpc.stub.AbstractFutureStub<GatewayGrpc.GatewayFutureStub>

 The Gateway API for evaluating and submitting transactions via the gateway.
 Transaction evaluation (query) requires the invocation of the Evaluate service
 Transaction submission (ledger updates) is a two step process invoking Endorse
 followed by Submit. A third step, invoking CommitStatus, is required if the
 clients wish to wait for a Transaction to be committed.
 The proposal and transaction must be signed by the client before each step.
 

Nested Class Summary

Nested classes/interfaces inherited from class io.grpc.stub.AbstractStub

io.grpc.stub.AbstractStub.StubFactory<T extends io.grpc.stub.AbstractStub<T>>

Method Summary

Modifier and Type	Method and Description
com.google.common.util.concurrent.ListenableFuture<CommitStatusResponse>	commitStatus(SignedCommitStatusRequest request) The CommitStatus service will indicate whether a prepared transaction previously submitted to the Submit service has been committed.
com.google.common.util.concurrent.ListenableFuture<EndorseResponse>	endorse(EndorseRequest request) The Endorse service passes a proposed transaction to the gateway in order to obtain sufficient endorsement.
com.google.common.util.concurrent.ListenableFuture<EvaluateResponse>	evaluate(EvaluateRequest request) The Evaluate service passes a proposed transaction to the gateway in order to invoke the transaction function and return the result to the client.
com.google.common.util.concurrent.ListenableFuture<SubmitResponse>	submit(SubmitRequest request) The Submit service will process the prepared transaction returned from Endorse service once it has been signed by the client.

Methods inherited from class io.grpc.stub.AbstractFutureStub

newStub, newStub

Methods inherited from class io.grpc.stub.AbstractStub

getCallOptions, getChannel, withCallCredentials, withChannel, withCompression, withDeadline, withDeadlineAfter, withExecutor, withInterceptors, withMaxInboundMessageSize, withMaxOutboundMessageSize, withOption, withWaitForReady

Methods inherited from class java.lang.Object

equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Method Detail

endorse

public com.google.common.util.concurrent.ListenableFuture<EndorseResponse> endorse(EndorseRequest request)

 The Endorse service passes a proposed transaction to the gateway in order to
 obtain sufficient endorsement.
 The gateway will determine the endorsement plan for the requested chaincode and
 forward to the appropriate peers for endorsement. It will return to the client a
 prepared transaction in the form of an Envelope message as defined
 in common/common.proto. The client must sign the contents of this envelope
 before invoking the Submit service.
 

submit

public com.google.common.util.concurrent.ListenableFuture<SubmitResponse> submit(SubmitRequest request)

 The Submit service will process the prepared transaction returned from Endorse service
 once it has been signed by the client. It will wait for the transaction to be submitted to the
 ordering service but the client must invoke the CommitStatus service to wait for the transaction
 to be committed.
 

commitStatus

public com.google.common.util.concurrent.ListenableFuture<CommitStatusResponse> commitStatus(SignedCommitStatusRequest request)

 The CommitStatus service will indicate whether a prepared transaction previously submitted to
 the Submit service has been committed. It will wait for the commit to occur if it hasn’t already
 committed.
 

evaluate

public com.google.common.util.concurrent.ListenableFuture<EvaluateResponse> evaluate(EvaluateRequest request)

 The Evaluate service passes a proposed transaction to the gateway in order to invoke the
 transaction function and return the result to the client. No ledger updates are made.
 The gateway will select an appropriate peer to query based on block height and load.