class ClientBidiReactor

Activate the RPC and initiate any reads or writes that have been Start'ed

before this call. All streaming RPCs issued by the client MUST have

StartCall invoked on them (even if they are canceled) as this call is the

activation of their lifecycle.

Initiate a read operation (or post it for later initiation if StartCall

has not yet been invoked).

Parameters

Initiate a write operation (or post it for later initiation if StartCall

has not yet been invoked).

Parameters

Initiate/post a write operation with specified options.

Parameters

Initiate/post a write operation with specified options and an indication

that this is the last write (like StartWrite and StartWritesDone, merged).

Note that calling this means that no more calls to StartWrite,

StartWriteLast, or StartWritesDone are allowed.

Parameters

Indicate that the RPC will have no more write operations. This can only be

issued once for a given RPC. This is not required or allowed if

StartWriteLast is used since that already has the same implication.

Note that calling this means that no more calls to StartWrite,

StartWriteLast, or StartWritesDone are allowed.

Holds are needed if (and only if) this stream has operations that take

place on it after StartCall but from outside one of the reactions

(OnReadDone, etc). This is _not_ a common use of the streaming API.

Holds must be added before calling StartCall. If a stream still has a hold

in place, its resources will not be destroyed even if the status has

already come in from the wire and there are currently no active callbacks

outstanding. Similarly, the stream will not call OnDone if there are still

holds on it.

For example, if a StartRead or StartWrite operation is going to be

initiated from elsewhere in the application, the application should call

AddHold or AddMultipleHolds before StartCall. If there is going to be,

for example, a read-flow and a write-flow taking place outside the

reactions, then call AddMultipleHolds(2) before StartCall. When the

application knows that it won't issue any more read operations (such as

when a read comes back as not ok), it should issue a RemoveHold(). It

should also call RemoveHold() again after it does StartWriteLast or

StartWritesDone that indicates that there will be no more write ops.

The number of RemoveHold calls must match the total number of AddHold

calls plus the number of holds added by AddMultipleHolds.

The argument to AddMultipleHolds must be positive.

Notifies the application that all operations associated with this RPC

have completed and all Holds have been removed. OnDone provides the RPC

status outcome for both successful and failed RPCs and will be called in

all cases. If it is not called, it indicates an application-level problem

(like failure to remove a hold).

Parameters

Notifies the application that a read of initial metadata from the

server is done. If the application chooses not to implement this method,

it can assume that the initial metadata has been read before the first

call of OnReadDone or OnDone.

Parameters

Notifies the application that a StartRead operation completed.

Parameters

Notifies the application that a StartWrite or StartWriteLast operation

completed.

Parameters

Notifies the application that a StartWritesDone operation completed. Note

that this is only used on explicit StartWritesDone operations and not for

those that are implicitly invoked as part of a StartWriteLast.

Parameters