proxygen
|
#include <MockAsyncTransport.h>
Public Member Functions | |
MOCK_METHOD0 (writeSuccess_, void()) | |
void | writeSuccess () noexceptoverride |
MOCK_METHOD2 (writeErr_, void(size_t, const AsyncSocketException &)) | |
void | writeErr (size_t size, const AsyncSocketException &ex) noexceptoverride |
![]() | |
virtual | ~WriteCallback ()=default |
Definition at line 113 of file MockAsyncTransport.h.
folly::test::MockWriteCallback::MOCK_METHOD0 | ( | writeSuccess_ | , |
void() | |||
) |
folly::test::MockWriteCallback::MOCK_METHOD2 | ( | writeErr_ | , |
void(size_t, const AsyncSocketException &) | |||
) |
|
inlineoverridevirtualnoexcept |
writeError() will be invoked if an error occurs writing the data.
bytesWritten | The number of bytes that were successfull |
ex | An exception describing the error that occurred. |
Implements folly::AsyncWriter::WriteCallback.
Definition at line 121 of file MockAsyncTransport.h.
References folly::size().
|
inlineoverridevirtualnoexcept |
writeSuccess() will be invoked when all of the data has been successfully written.
Note that this mainly signals that the buffer containing the data to write is no longer needed and may be freed or re-used. It does not guarantee that the data has been fully transmitted to the remote endpoint. For example, on socket-based transports, writeSuccess() only indicates that the data has been given to the kernel for eventual transmission.
Implements folly::AsyncWriter::WriteCallback.
Definition at line 116 of file MockAsyncTransport.h.
References MOCK_METHOD2.