From: Robert Ramey (ramey_at_[hidden])
Date: 2005-03-29 11:01:38
I refreshed my memory re aio.h and found it uses no callback.
Start an asynchronous read operation
Start an asynchronous write operation
Start a list of asynchronous I/O operations
Wait for completion of one or more asynchronous I/O operations
Retrieve the error status of an asynchronous I/O operation
Retrieve the return status of an asynchronous I/O operation and free any
associated system resources
Request cancellation of a pending asynchronous I/O operation
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.
> 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.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk