I refreshed my memory re aio.h and found it uses no callback. aio_read Start an asynchronous read operation aio_write Start an asynchronous write operation lio_listio Start a list of asynchronous I/O operations aio_suspend Wait for completion of one or more asynchronous I/O operations aio_error Retrieve the error status of an asynchronous I/O operation aio_return Retrieve the return status of an asynchronous I/O operation and free any associated system resources aio_cancel Request cancellation of a pending asynchronous I/O operation aio_fsync Initiate synchronization of the media image of a file to which asynchronous operations have been addressed The question here is: iIs aio.h interface not sufficient in some way? If not, what facility is it missing? If it is sufficient, then just depend on the available implementation or re-implement the interface in the most convenient way. Robert Ramey Boris wrote:
I am not sure if I understand correctly. Just as Don I think we can't get around threads when we have callbacks. I don't know about Windows but the callback in aio (Posix) is done by creating a new thread.