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
but I was wondering what would be required to support writing recursive data structures asynchronously to the socket, like mentioned here. Should we make the write_frame method synchronous, and use tokio channels with synchronous methods on the sender? But then maybe it could get filled up if IO is slow?
Then what would be the most efficient / idiomatic way to tackle this?
That would allow support for sending array frames containing array frames, which is frequent in redis. I'd be glad to submit a PR if it is deemed useful for the tutorial repo.
The text was updated successfully, but these errors were encountered:
The cleanest way to do it would be to rewrite it to use tokio_util::codec, which doesn't have these challenges. Another option is to use boxing to allow recursion.
I don't know where the best place to ask this is,
but I was wondering what would be required to support writing recursive data structures asynchronously to the socket, like mentioned here. Should we make the write_frame method synchronous, and use tokio channels with synchronous methods on the sender? But then maybe it could get filled up if IO is slow?
Then what would be the most efficient / idiomatic way to tackle this?
That would allow support for sending array frames containing array frames, which is frequent in redis. I'd be glad to submit a PR if it is deemed useful for the tutorial repo.
The text was updated successfully, but these errors were encountered: