On 30 Aug 2015 at 23:05, Gruenke,Matt wrote:
Boost.AFIO provides a pure portable POSIX file i/o backend and specialised file i/o backends making use of host OS asynchronous file i/o facilities are provided for: ... * Linux KAIO (planned, would reduce thread pool blocking for read() and write() only) * POSIX AIO, suitable for BSD only (planned, would reduce thread pool blocking for read() and write() only)
This leaves me feeling that it's a solution that's searching for a problem. I think Niall has done great work on it, from the little I've seen. But if I want a fast, disk-based database, I'll use sqlite - which does a lot more for me - not go straight to the filesystem.
I think this would be a valid rationale if I were presenting Boost.KeyValueStore. But to analogise, you are effectively saying "I don't see a use for Boost.Atomic because a spinlocked STL container does a lot more for me than Boost.Lockfree containers". Which may or may not be true. But the point here is that like Boost.Atomic, until it's in Boost nobody has any idea what exciting things people might build with it. Boost.Atomic on its own merit seems to have little use.
What I saw of docs looked good, and I was glad to see benchmarks. More generally, I also appreciate Niall's participation in the boost (and ASIO) community.
Thanks for the appreciation. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/