Feature #237
Is there a usecase for vectored I/O?
| Status: | New | Start date: | 08/07/2012 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - | |||
| Component: |
Description
We currently don't provide NIO's interface to readv/writev (aka vectored io, aka scattered reading and gathered writes).
Is there a use case for it?
History
#1 Updated by hans over 5 years ago
I'm sure there is, but since we haven't needed it yet, I think its low priority. We haven't entirely proven IOCipher yet, so I think its important that we first get one approach working really well. Once that's done, we can say that this whole libsqlfs approach actually works. Then we can implement all of the various other parts of this API knowing that the work won't be thrown away.
#2 Updated by abeluck over 5 years ago
Yup, I agree. Keeping this one alive for reference. It's already marked Low priority.
#3 Updated by hans almost 4 years ago
- Target version set to 61
#4 Updated by hans almost 4 years ago
- Target version deleted (
61)