4 ms·

Netstrings are for this exact use case: http://cr.yp.to/proto/netstrings.txt http://cr.yp.to/proto/netstrings.txt

• viraptor 11y ago
  Actually this proposal is quite bad compared to simple "<4 bytes size><size bytes contents>". If you use netstrings recursively like djb recommends, you will end up copying / reallocing the strings many times. Since your top-level length depends on the lower level length, you cannot send it without actually calculating the whole contents. Asn1 DER has the same issue because of the weird size encoding. RIFF is a bit better https://en.wikipedia.org/wiki/Resource_Interchange_File_Format https://en.wikipedia.org/wiki/Resource_Interchange_File_Form... with strict length,tag,contents format.
  • zrail 11y ago
    Wasn't suggesting they use the recursive feature. Just a flat netstring for the data segments, sort of how the Redis and Memcached protocols work.
• krakensden 11y ago
  I think tnetstrings are a pretty reasonable improvement, too https://github.com/rfk/tnetstring/ https://github.com/rfk/tnetstring/