[ViewVC] Diff of: cvs/IO-AIO/README

Comparing IO-AIO/README (file contents):
Revision 1.9 by root, Tue Aug 16 23:33:38 2005 UTC vs.
Revision 1.10 by root, Wed Aug 17 05:26:20 2005 UTC

     aio_write $fh,$offset,$length, $data,$dataoffset,$callback
         Reads or writes "length" bytes from the specified "fh" and "offset"
         into the scalar given by "data" and offset "dataoffset" and calls
         the callback without the actual number of bytes read (or -1 on
         error, just like the syscall).
+        The $data scalar *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).
         Example: Read 15 bytes at offset 7 into scalar $buffer, starting at
         offset 0 within the scalar:
            aio_read $fh, 7, 15, $buffer, 0, sub {
         if you set this to a relatively low number, such as 100.
         Under normal circumstances you don't need to call this function.
   FORK BEHAVIOUR
-    IO::AIO handles all outstanding AIO requests before the fork, destroys
+    Before the fork IO::AIO enters a quiescent state where no requests can
-    all AIO threads, and recreates them in both the parent and the child
+    be added in other threads and no results will be processed. After the
-    after the fork.
+    fork the parent simply leaves the quiescent state and continues
+    request/result processing, while the child clears the request/result
+    queue and starts the same number of threads as were in use by the
+    parent.
 SEE ALSO
     Coro, Linux::AIO.
 AUTHOR

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines