class CompleteOutputBufferPartialSettings
Defined at line 1292 of file fidling/gen/sdk/fidl/fuchsia.media/fuchsia.media/cpp/fidl/fuchsia.media/cpp/markers.h
After SetOutputBufferPartialSettings(), the server won't send
OnOutputConstraints(), OnOutputFormat(), OnOutputPacket(), or
OnOutputEndOfStream() until after the client sends
CompleteOutputBufferPartialSettings().
This message isn't permitted after AddBuffer. When using dynamic buffers
the server can send OnOutputConstraints, OnOutputFormat, OnOutputPacket,
or OnOutputEndOfStream at any time after the first QueueInputPacket. In
the case of OnOutputPacket there must also be at least one output buffer
that's been added but not yet fully removed (RemoveBuffer not yet
complete).
Some clients may be able to send CompleteOutputBufferPartialSettings()
immediately after SetOutputBufferPartialSettings() - in that case the
client needs to be prepared to receive output without knowing the buffer
count or packet count yet - such clients may internally delay processing
the received output until the client has heard from sysmem (which is
when the client will learn the buffer count and packet count).
Other clients may first wait for sysmem to allocate, prepare to receive
output, and then send CompleteOutputBufferPartialSettings().
Public Members
static const bool kHasClientToServerstatic const bool kHasClientToServerBodystatic const bool kHasServerToClientstatic const bool kHasServerToClientBodystatic const bool kHasNonEmptyUserFacingResponsestatic const bool kHasDomainErrorstatic const bool kHasFrameworkErrorstatic const uint64_t kOrdinal