[ViewVC] Diff of: cvs/IO-AIO/AIO.pm

Comparing IO-AIO/AIO.pm (file contents):
Revision 1.30 by root, Wed Aug 17 04:47:38 2005 UTC vs.
Revision 1.31 by root, Wed Aug 17 05:06:59 2005 UTC

 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).
+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).
 Example: Read 15 bytes at offset 7 into scalar C<$buffer>, starting at
 offset C<0> within the scalar:
    aio_read $fh, 7, 15, $buffer, 0, sub {
       $_[0] > 0 or die "read error: $!";
 1;
 =head2 FORK BEHAVIOUR
-Before the fork IO::AIO first handles all outstanding requests - if other
+Before the fork IO::AIO enters a quiescent state where no requests can be
-threads add requests during this period, this time is prolonged. It then
+added in other threads and no results will be processed. After the fork
-enters a quiescent state where no requests can be added in other threads
+the parent simply leaves the quiescent state and continues request/result
-and no results will be processed. After the fork the parent simply leaves
+processing, while the child clears the request/result queue and starts the
-the quiescent state and continues request processing, while the child
-starts the same number of threads as were in use by the parent.
+same number of threads as were in use by the parent.
 =head1 SEE ALSO
 L<Coro>, L<Linux::AIO>.

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