pub struct Payload {
pub epoch: Epoch,
pub pipeline_id: PipelineId,
pub display_list_data: Vec<u8>,
}
Fields§
§epoch: Epoch
An epoch used to get the proper payload for a pipeline id frame request.
TODO(emilio): Is this still relevant? We send the messages for the same pipeline in order, so we shouldn’t need it. Seems like this was only wallpapering (in most cases) the underlying problem in #991.
pipeline_id: PipelineId
A pipeline id to key the payload with, along with the epoch.
display_list_data: Vec<u8>
Implementations§
Source§impl Payload
impl Payload
Sourcepub fn construct_data(
epoch: Epoch,
pipeline_id: PipelineId,
dl_data: &[u8],
) -> Vec<u8> ⓘ
pub fn construct_data( epoch: Epoch, pipeline_id: PipelineId, dl_data: &[u8], ) -> Vec<u8> ⓘ
Convert the payload to a raw byte vector, in order for it to be efficiently shared via shmem, for example. This is a helper static method working on a slice.
Trait Implementations§
Auto Trait Implementations§
impl Freeze for Payload
impl RefUnwindSafe for Payload
impl Send for Payload
impl Sync for Payload
impl Unpin for Payload
impl UnwindSafe for Payload
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Mutably borrows from an owned value. Read more