You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems a bit overkill to use Bytes for encoding. Bytes makes more sense in a situation where data is being streamed (e.g., over TCP) with one thread pushing to the buffer while another reads. With the ability to read an entire datagram at once the only niceity is
the API, but with an unnecessary Arc overhead.
Additionally, I'm fine with an API that requires the user to specify the buffer size and error if the buffer would be overwhelmed. That's usually an indication that we should reject the data to begin with.
The text was updated successfully, but these errors were encountered:
It seems a bit overkill to use Bytes for encoding. Bytes makes more sense in a situation where data is being streamed (e.g., over TCP) with one thread pushing to the buffer while another reads. With the ability to read an entire datagram at once the only niceity is
the API, but with an unnecessary Arc overhead.
Additionally, I'm fine with an API that requires the user to specify the buffer size and error if the buffer would be overwhelmed. That's usually an indication that we should reject the data to begin with.
The text was updated successfully, but these errors were encountered: