Replies: 1 comment
-
I think it would be a good idea to have a separate crate with IoBuf/Slice and owned IO traits. We could add a new crate to the tokio org for this and re-export it through uring. @carllerche how do you feel about doing this? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Thanks for your work on bringing io-uring to async Rust! Inspired by this project, I wrote
tokio-iocp
to bring Windows IOCP to tokio. Both framework, io-uring and IOCP, are proactors, and the wrapper projects needs many similar types and traits.For example, the buffers are passed into the read/write methods, which could be abstracted to new traits, maybe
AsyncReadOwned
andAsyncWriteOwned
. The traits for the buffers,IoBuf
andIoBufMut
, together with typeSlice
, could also be shared between the wrappers. The frameworks on different OS differ, but the wrapper API could be the same, and finally we can make our way to unified API, for example,tokio-proactor
.I'm asking that if you could split some general types, mainly
IoBuf*
,Slice
, and if possible, some general IO traits, to a standalone crate. And if you are interested in, you can take a look intotokio-iocp
, whose API is very much liketokio-uring
. Anyway, thank you all for your contributions for Rust!Beta Was this translation helpful? Give feedback.
All reactions