pub trait RequestBody {
type ResponseBody;
const API_KEY: ApiKey;
const API_VERSION_RANGE: ApiVersionRange;
const FIRST_TAGGED_FIELD_IN_REQUEST_VERSION: ApiVersion;
const FIRST_TAGGED_FIELD_IN_RESPONSE_VERSION: ApiVersion = Self::FIRST_TAGGED_FIELD_IN_REQUEST_VERSION;
}Expand description
Specifies a request body.
Required Associated Constants§
Sourceconst API_VERSION_RANGE: ApiVersionRange
const API_VERSION_RANGE: ApiVersionRange
Supported version range.
From this range and the range that the broker reports, we will pick the highest version that both support.
Sourceconst FIRST_TAGGED_FIELD_IN_REQUEST_VERSION: ApiVersion
const FIRST_TAGGED_FIELD_IN_REQUEST_VERSION: ApiVersion
The first version of the messages (not of the header) that uses tagged fields, if any.
To determine the version just look for the _tagged_fields or TAG_BUFFER in the protocol description.
This will be used to control which request and response header versions will be used.
It’s OK to specify a version here that is larger then the highest supported version.
Provided Associated Constants§
Sourceconst FIRST_TAGGED_FIELD_IN_RESPONSE_VERSION: ApiVersion = Self::FIRST_TAGGED_FIELD_IN_REQUEST_VERSION
const FIRST_TAGGED_FIELD_IN_RESPONSE_VERSION: ApiVersion = Self::FIRST_TAGGED_FIELD_IN_REQUEST_VERSION
Normally the same as FIRST_TAGGED_FIELD_IN_REQUEST_VERSION but
there are some special snowflakes.
Required Associated Types§
Sourcetype ResponseBody
type ResponseBody
The response type that will follow when issuing this request.
Dyn Compatibility§
This trait is not dyn compatible.
In older versions of Rust, dyn compatibility was called "object safety", so this trait is not object safe.