TestServiceStub is the main asynchronous stub, and is built around the idea
of the Observable / Observer pattern. RxJava uses this pattern, for
instance.
One thing to note, if you don't like those stubs, you can call the
ClientCall and ClientCall.Listener directly. You can't use the generated
stub library, but it does have async behavior. (Personally, I use it, but
copy-paste the MethodDescriptors from the generated code.)
On Monday, November 12, 2018 at 4:07:56 AM UTC-8, qplc wrote:
>
> Hi,
>
> I've implemented below service definition in my grpc server/client
> application.
>
> service TestService {
> rpc testRPCCall(stream Test) returns (stream Test) {}
> }
>
> I found below stubs can be implemented on proto file compilation.
> TestServiceGrpc.TestServiceStub
> TestServiceGrpc.TestServiceBlockingStub
> TestServiceGrpc.TestServiceFutureStub
> TestServiceGrpc.TestServiceImplBase
>
> I want to adapt asynchronous behavior of rpc calls. But, I'm not sure
> which one of above should be implemented. Is it mandatory to stream a rpc
> call(stream Test) as mentioned in above service definition for asynchronous
> implementation?
>
>
> Thanks in advance.
>
>
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/85a5cd0e-bb41-4963-8ae4-300586a65abd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
