Brian Sipos

A workaround is to set "allow_insecure => true" but this defeats the authentication of TLS.

Yes, just exposing a Tell interface with an appropriate explanation of what the offset represents (the position of the start of the next item, break, or EOF depending on what's...

Having a Tell interface for the streaming encoder would also be valuable for certain uses. Specifically, there are CRC byte-string items as part of [RFC 9171](https://www.rfc-editor.org/rfc/rfc9171.html#section-4.3) block encodings that would...

I ran into this same issue and see this as a split of responsibility between this library and the application using it. Meaning _something_ should account for all of the...

Thanks! I thought it was just the docs and not the interface.

One way to deal with this kind of thing is to not include _any_ parameter or result handling in the ASB and instead defer all context-id-specific handling to a class...

My actual desire is to have a sequential bytestring builder the same way that the `m_string_t` allows sequential text string building. I could do this with an M-Array of `uint8_t`...

Similar to how M-DICT has two variants (one for dictionary and one for set logic) maybe the third option with a different set of `#define` for whatever functions are safe...

> Shall the bytestring container allow read only sequential byte or read/write sequential bytes? > > Read and write is desired. Because the current string API has a efficient logic...

> Here is the proposed API for a bstring container: I think this API is quite good and covers many possible manipulations including the pushing and popping of multi-byte chunks....