Lines Matching full:packet
86 mechanisms that provide their own framing and packet-separation
91 properly separate data back into packets at the original packet
92 boundaries without relying on decoding to find packet boundaries.</p>
100 packet boundary marking, high-level framing, sync and seeking.</li>
126 packet segments into a variable length page preceded by a page
137 <h3>Packet segmentation</h3>
142 page data need not be disturbed, even when a packet spans page
145 <p>The raw packet is logically divided into [n] 255 byte segments and a
146 last fractional segment of < 255 bytes. A packet size may well
155 raw packet:
164 value for a packet is always the value that is less than 255. Note
165 that this encoding both avoids imposing a maximum packet size as well
167 simply using two bytes at the head of every packet and having a max
168 packet size of 32k. Small packets (<255, the typical case) are
175 follows in the packet, and a value of < 255 marks the end of the
176 packet after that many additional bytes. A packet of 255 bytes (or a
180 raw packet:
187 <p>Note also that a 'nil' (zero length) packet is not an error; it
200 <p>After segmenting a packet, the encoder may decide not to place all the
205 the next packet segment, thus continuing the packet (data in the
206 packet body must also correspond properly to the lacing values in the
207 spanned pages. The segment data in the first packet corresponding to
208 the lacing values of the first page belong in that page; packet
214 segment table continues rather than begins a packet; a header flag of
215 0x01 is set to indicate a continued packet. Although mandatory, it
217 preceding segment table to determine if the packet is new or
221 recovery in the event that the packet originates in a corrupt
225 <p>Note that a packet can span an arbitrary number of pages; the above
227 'zero termination' on a packet size that is an even multiple of 255
229 zero-length continuation of the current packet. The header flag
230 should be set to 0x01 to indicate that the packet spanned, even though
236 sizes can be handled within the model; placing packet size
240 <p>The main point behind tracking individual packets (and packet
242 explicit knowledge of packet size. An example is simple bandwidth
244 if the packet is arranged so that the least sensitive portion of the
250 of the packet data (ie, making the packet segmentation process a
252 packet data. The encoder buffers packet data until it finishes a
254 buffered packet segments.</p>
289 5 bitflags: 0x01: unset = fresh packet
290 set = continued packet
400 <h4>segment_table (containing packet lacing values)</h4>
402 <p>The lacing values for each packet segment physically appearing in
414 lacing values in the segment table. Packet data segments follow
419 packet recovery in the streaming layer adds approximately .5-1%
