Byte Frame Chunk Carry Tool
Advance one fixed-byte streaming frame chunk with explicit incomplete carry, emitting complete frames and retaining the new tail; no sync search.
Description
Advance one fixed-byte streaming frame chunk with explicit incomplete carry, emitting complete frames and retaining the new tail; no sync search.
A fixed-size streaming parser can emit complete frames and carry an incomplete suffix into its next call.
When to use this tool
Advance one fixed-byte streaming frame chunk with explicit incomplete carry, emitting complete frames and retaining the new tail; no sync search.
- Prepare the supplied carry, chunk, frameBytes fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter carry, chunk, frameBytes. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.frames, result.carry. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require frameBytes from 1 to 128 and carry shorter than one frame. Concatenate carry and chunk, emit floor(total length/frameBytes) complete slices and return the remaining suffix as carry.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| carry | carry. | List of integers from 0 to 255; at most 128 bytes |
| chunk | chunk. | List of integers from 0 to 255; at most 128 bytes |
| frameBytes | frame bytes. | Integer from 1 to 128 inclusive |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.frames | The frames list in the ordering and representation described above. |
| result.carry | The carry list in the ordering and representation described above. |
{
"input": {
"carry": [
1
],
"chunk": [
2,
3,
4
],
"frameBytes": 3
},
"output": {
"result": {
"frames": [
[
1,
2,
3
]
],
"carry": [
4
]
}
}
}Limitations and assumptions
- No state is retained between calls; pass the returned carry explicitly. No delimiter, synchronization or variable-length protocol is recognized.
- All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
- JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.
Alternative or Complementary methods
Use a stateful protocol parser when processing partial streams or validating complete packets. Retain the declared prefix width, byte order and payload-versus-frame boundary convention when composing these operations.
References
Similar or alternative tools
- Byte Frame Chunk Rejoin Tool
Rejoin explicit bounded byte chunks and report each chunk’s half-open source span, preserving empty-chunk provenance.
- Byte Frame Delimiter Coverage Check
Compare explicit byte delimiter observations against caller-declared boundary positions, retaining both undeclared delimiters and false boundary claims.