Netstring Byte Record Decoder
Decode exactly one complete binary netstring with canonical ASCII decimal length and terminal comma; no concatenated records or leading-zero lengths.
Description
Decode exactly one complete binary netstring with canonical ASCII decimal length and terminal comma; no concatenated records or leading-zero lengths.
A netstring encodes a byte payload as decimal length, colon, payload and comma. Length counts octets rather than decoded characters.
When to use this tool
Decode exactly one complete binary netstring with canonical ASCII decimal length and terminal comma; no concatenated records or leading-zero lengths.
- Prepare the supplied bytes 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 bytes. 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.payload. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require a nonempty decimal length before the first colon, without leading zeros except zero. Require exactly that many payload bytes followed by one final comma and return the payload.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| bytes | bytes. | List of integers from 0 to 255; at most 128 bytes |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.payload | The payload list in the ordering and representation described above. |
{
"input": {
"bytes": [
50,
58,
0,
255,
44
]
},
"output": {
"result": {
"payload": [
0,
255
]
}
}
}Limitations and assumptions
- The input must contain exactly one complete record and at most 128 bytes. No trailing record, Unicode decoding or transport buffering is handled.
- 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
- Netstring Byte Record Encoder
Encode a single byte netstring with ASCII decimal byte length, colon and comma; binary payload bytes are not converted to text.
- 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.