[ViewVC] Diff of: cvs/AnyEvent-Fork-RPC/RPC.pm

Comparing AnyEvent-Fork-RPC/RPC.pm (file contents):
Revision 1.14 by root, Thu Apr 18 13:11:12 2013 UTC vs.
Revision 1.15 by root, Thu Apr 18 13:15:23 2013 UTC

 The default server used in the child does all I/O blockingly, and only
 allows a single RPC call to execute concurrently.
 Setting C<async> to a true value switches to another implementation that
-uses L<AnyEvent> in the child and allows multiple concurrent RPC calls.
+uses L<AnyEvent> in the child and allows multiple concurrent RPC calls (it
+does not support recursion in the event loop however, blocking condvar
+calls will fail).
 The actual API in the child is documented in the section that describes
 the calling semantics of the returned C<$rpc> function.
 If you want to pre-load the actual back-end modules to enable memory
 are queued and the jobs are slow, they will all run concurrently. The
 child must implement some queueing/limiting mechanism if this causes
 problems. Alternatively, the parent could limit the amount of rpc calls
 that are outstanding.
+Blocking use of condvars is not supported.
 Using event-based modules such as L<IO::AIO>, L<Gtk2>, L<Tk> and so on is
 easy.
 =back

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