|
GRPC C++
1.4.0
|
Async client-side interface for bi-directional streaming, where the outgoing message stream going to the server has messages of type W, and the incoming message stream coming from the server has messages of type R. More...
#include <async_stream.h>
Public Member Functions | |
| void | ReadInitialMetadata (void *tag) override |
| See the ClientAsyncStreamingInterface.ReadInitialMetadata method for semantics of this method. More... | |
| void | Read (R *msg, void *tag) override |
| Read a message of type R into msg. More... | |
| void | Write (const W &msg, void *tag) override |
| Request the writing of msg with identifying tag tag. More... | |
| void | Write (const W &msg, WriteOptions options, void *tag) override |
| Request the writing of msg using WriteOptions options with identifying tag tag. More... | |
| void | WritesDone (void *tag) override |
| Signal the client is done with the writes (half-close the client stream). More... | |
| void | Finish (Status *status, void *tag) override |
| See the ClientAsyncStreamingInterface.Finish method for semantics. More... | |
Public Member Functions inherited from grpc::ClientAsyncStreamingInterface | |
| virtual | ~ClientAsyncStreamingInterface () |
Public Member Functions inherited from grpc::AsyncWriterInterface< W > | |
| virtual | ~AsyncWriterInterface () |
| void | WriteLast (const W &msg, WriteOptions options, void *tag) |
| Request the writing of msg and coalesce it with the writing of trailing metadata, using WriteOptions options with identifying tag tag. More... | |
Public Member Functions inherited from grpc::AsyncReaderInterface< R > | |
| virtual | ~AsyncReaderInterface () |
Static Public Member Functions | |
| static ClientAsyncReaderWriter * | Create (ChannelInterface *channel, CompletionQueue *cq, const RpcMethod &method, ClientContext *context, void *tag) |
| Create a stream and write the first request out. More... | |
| static void | operator delete (void *ptr, std::size_t size) |
Async client-side interface for bi-directional streaming, where the outgoing message stream going to the server has messages of type W, and the incoming message stream coming from the server has messages of type R.
|
inlinestatic |
Create a stream and write the first request out.
tag will be notified on cq when the call has been started (i.e. intitial metadata sent). Note that context will be used to fill in custom initial metadata used to send to the server when starting the call.
|
inlineoverridevirtual |
See the ClientAsyncStreamingInterface.Finish method for semantics.
Side effect
Implements grpc::ClientAsyncStreamingInterface.
|
inlinestatic |
|
inlineoverridevirtual |
Read a message of type R into msg.
Completion will be notified by tag on the associated completion queue. This is thread-safe with respect to Write or WritesDone methods. It should not be called concurrently with other streaming APIs on the same stream. It is not meaningful to call it concurrently with another AsyncReaderInterface::Read on the same stream since reads on the same stream are delivered in order.
| [out] | msg | Where to eventually store the read message. |
| [in] | tag | The tag identifying the operation. |
Side effect: note that this method attempt to receive initial metadata for a stream if it hasn't yet been received.
Implements grpc::AsyncReaderInterface< R >.
|
inlineoverridevirtual |
See the ClientAsyncStreamingInterface.ReadInitialMetadata method for semantics of this method.
Side effect:
Implements grpc::ClientAsyncStreamingInterface.
|
inlineoverridevirtual |
Request the writing of msg with identifying tag tag.
Only one write may be outstanding at any given time. This means that after calling Write, one must wait to receive tag from the completion queue BEFORE calling Write again. This is thread-safe with respect to AsyncReaderInterface::Read
| [in] | msg | The message to be written. |
| [in] | tag | The tag identifying the operation. |
Implements grpc::AsyncWriterInterface< W >.
|
inlineoverridevirtual |
Request the writing of msg using WriteOptions options with identifying tag tag.
Only one write may be outstanding at any given time. This means that after calling Write, one must wait to receive tag from the completion queue BEFORE calling Write again. WriteOptions options is used to set the write options of this message. This is thread-safe with respect to AsyncReaderInterface::Read
| [in] | msg | The message to be written. |
| [in] | options | The WriteOptions to be used to write this message. |
| [in] | tag | The tag identifying the operation. |
Implements grpc::AsyncWriterInterface< W >.
|
inlineoverridevirtual |
Signal the client is done with the writes (half-close the client stream).
Thread-safe with respect to AsyncReaderInterface::Read
| [in] | tag | The tag identifying the operation. |
Implements grpc::ClientAsyncReaderWriterInterface< W, R >.
1.8.6