--- IO-AIO/AIO.pm	2007/06/01 05:52:59	1.107
+++ IO-AIO/AIO.pm	2007/06/03 09:44:17	1.109
@@ -64,12 +64,11 @@
 on a RAID volume or over NFS when you do a number of stat operations
 concurrently.
 
-While most of this works on all types of file descriptors (for example
-sockets), using these functions on file descriptors that support
-nonblocking operation (again, sockets, pipes etc.) is very inefficient or
-might not work (aio_read fails on sockets/pipes/fifos). Use an event loop
-for that (such as the L<Event|Event> module): IO::AIO will naturally fit
-into such an event loop itself.
+While most of this works on all types of file descriptors (for
+example sockets), using these functions on file descriptors that
+support nonblocking operation (again, sockets, pipes etc.) is very
+inefficient. Use an event loop for that (such as the L<Event|Event>
+module): IO::AIO will naturally fit into such an event loop itself.
 
 In this version, a number of threads are started that execute your
 requests and signal their completion. You don't need thread support
@@ -81,10 +80,10 @@
 aio_write, so the remaining functionality would have to be implemented
 using threads anyway.
 
-Although the module will work with in the presence of other (Perl-)
-threads, it is currently not reentrant in any way, so use appropriate
-locking yourself, always call C<poll_cb> from within the same thread, or
-never call C<poll_cb> (or other C<aio_> functions) recursively.
+Although the module will work in the presence of other (Perl-) threads,
+it is currently not reentrant in any way, so use appropriate locking
+yourself, always call C<poll_cb> from within the same thread, or never
+call C<poll_cb> (or other C<aio_> functions) recursively.
 
 =head2 EXAMPLE
 
@@ -327,14 +326,22 @@
 
 =item aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval)
 
-Reads or writes C<length> bytes from the specified C<fh> and C<offset>
-into the scalar given by C<data> and offset C<dataoffset> and calls the
+Reads or writes C<$length> bytes from the specified C<$fh> and C<$offset>
+into the scalar given by C<$data> and offset C<$dataoffset> and calls the
 callback without the actual number of bytes read (or -1 on error, just
 like the syscall).
 
+If C<$offset> is undefined, then the current file offset will be used (and
+updated), otherwise the file offset will not be changed by these calls.
+
+If C<$length>  is undefined in C<aio_write>, use the remaining length of C<$data>.
+
+If C<$dataoffset> is less than zero, it will be counted from the end of
+C<$data>.
+
 The C<$data> scalar I<MUST NOT> be modified in any way while the request
-is outstanding. Modifying it can result in segfaults or WW3 (if the
-necessary/optional hardware is installed).
+is outstanding. Modifying it can result in segfaults or World War III (if
+the necessary/optional hardware is installed).
 
 Example: Read 15 bytes at offset 7 into scalar C<$buffer>, starting at
 offset C<0> within the scalar: