One end of a connection between a gRPC client and server.
Endpoints are created when connections are established, and Endpoint operations are gRPC's primary means of communication.
Endpoints must use the provided MemoryAllocator for all data buffer memory allocations. gRPC allows applications to set memory constraints per Channel or Server, and the implementation depends on all dynamic memory allocation being handled by the quota system.
| virtual bool grpc_event_engine::experimental::EventEngine::Endpoint::Read |
( |
absl::AnyInvocable< void(absl::Status)> |
on_read, |
|
|
SliceBuffer * |
buffer, |
|
|
ReadArgs |
args |
|
) |
| |
|
pure virtual |
Reads data from the Endpoint.
When data is available on the connection, that data is moved into the buffer. If the read succeeds immediately, it returns true and the on_read callback is not executed. Otherwise it returns false and the on_read callback executes asynchronously when the read completes. The caller must ensure that the callback has access to the buffer when it executes. Ownership of the buffer is not transferred. Either an error is passed to the callback (like socket closed), or valid data is available in the buffer, but never both at the same time. Implementations that receive valid data must not throw that data away - that is, if valid data is received on the underlying endpoint, a callback will be made with that data available and an ok status.
There can be at most one outstanding read per Endpoint at any given time. An outstanding read is one in which the on_read callback has not yet been executed for some previous call to Read. If an attempt is made to call Read while a previous read is still outstanding, the EventEngine must abort.
For failed read operations, implementations should pass the appropriate statuses to on_read. For example, callbacks might expect to receive CANCELLED on endpoint shutdown.
| virtual bool grpc_event_engine::experimental::EventEngine::Endpoint::Write |
( |
absl::AnyInvocable< void(absl::Status)> |
on_writable, |
|
|
SliceBuffer * |
data, |
|
|
WriteArgs |
args |
|
) |
| |
|
pure virtual |
Writes data out on the connection.
If the write succeeds immediately, it returns true and the on_writable callback is not executed. Otherwise it returns false and the on_writable callback is called asynchronously when the connection is ready for more data. The Slices within the data buffer may be mutated at will by the Endpoint until on_writable is called. The data SliceBuffer will remain valid after calling Write, but its state is otherwise undefined. All bytes in data must have been written before calling on_writable unless an error has occurred.
There can be at most one outstanding write per Endpoint at any given time. An outstanding write is one in which the on_writable callback has not yet been executed for some previous call to Write. If an attempt is made to call Write while a previous write is still outstanding, the EventEngine must abort.
For failed write operations, implementations should pass the appropriate statuses to on_writable. For example, callbacks might expect to receive CANCELLED on endpoint shutdown.
Public Member Functions inherited from grpc_event_engine::experimental::Extensible