ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/AnyEvent-Fork-RPC/RPC.pm
(Generate patch)

Comparing AnyEvent-Fork-RPC/RPC.pm (file contents):
Revision 1.31 by root, Sat Aug 31 16:35:33 2013 UTC vs.
Revision 1.34 by root, Wed Nov 20 15:26:56 2013 UTC

… …
175you really I<are> done. 175you really I<are> done.
176 176
177=head2 Example 2: Asynchronous Backend 177=head2 Example 2: Asynchronous Backend
178 178
179This example implements multiple count-downs in the child, using 179This example implements multiple count-downs in the child, using
180L<AnyEvent> timers. While this is a bit silly (one could use timers in te 180L<AnyEvent> timers. While this is a bit silly (one could use timers in the
181parent just as well), it illustrates the ability to use AnyEvent in the 181parent just as well), it illustrates the ability to use AnyEvent in the
182child and the fact that responses can arrive in a different order then the 182child and the fact that responses can arrive in a different order then the
183requests. 183requests.
184 184
185It also shows how to embed the actual child code into a C<__DATA__> 185It also shows how to embed the actual child code into a C<__DATA__>
… …
391use Errno (); 391use Errno ();
392use Guard (); 392use Guard ();
393 393
394use AnyEvent; 394use AnyEvent;
395 395
396our $VERSION = 1.1; 396our $VERSION = 1.21;
397 397
398=item my $rpc = AnyEvent::Fork::RPC::run $fork, $function, [key => value...] 398=item my $rpc = AnyEvent::Fork::RPC::run $fork, $function, [key => value...]
399 399
400The traditional way to call it. But it is way cooler to call it in the 400The traditional way to call it. But it is way cooler to call it in the
401following way: 401following way:
… …
629 }; 629 };
630 630
631 my $module = "AnyEvent::Fork::RPC::" . ($arg{async} ? "Async" : "Sync"); 631 my $module = "AnyEvent::Fork::RPC::" . ($arg{async} ? "Async" : "Sync");
632 632
633 $self->require ($module) 633 $self->require ($module)
634 ->send_arg ($function, $arg{init}, $serialiser, $arg{done} || "CORE::exit") 634 ->send_arg ($function, $arg{init}, $serialiser, $arg{done} || "$module\::do_exit")
635 ->run ("$module\::run", sub { 635 ->run ("$module\::run", sub {
636 $fh = shift; 636 $fh = shift;
637 637
638 my ($id, $len); 638 my ($id, $len);
639 $rw = AE::io $fh, 0, sub { 639 $rw = AE::io $fh, 0, sub {
… …
786 786
787For the asynchronous backend, things are more complicated: Whenever it 787For the asynchronous backend, things are more complicated: Whenever it
788listens for another request by the parent, it might detect that the socket 788listens for another request by the parent, it might detect that the socket
789was closed (e.g. because the parent exited). It will sotp listening for 789was closed (e.g. because the parent exited). It will sotp listening for
790new requests and instead try to write out any remaining data (if any) or 790new requests and instead try to write out any remaining data (if any) or
791simply check whether the socket cna be written to. After this, the RPC 791simply check whether the socket can be written to. After this, the RPC
792process is effectively done - no new requests are incoming, no outstanding 792process is effectively done - no new requests are incoming, no outstanding
793request data can be written back. 793request data can be written back.
794 794
795Since chances are high that there are event watchers that the RPC server 795Since chances are high that there are event watchers that the RPC server
796knows nothing about (why else would one use the async backend if not for 796knows nothing about (why else would one use the async backend if not for
797the ability to register watchers?), the event loop would often happily 797the ability to register watchers?), the event loop would often happily
798continue. 798continue.
799 799
800This is why the asynchronous backend explicitly calls C<CORE::exit> when 800This is why the asynchronous backend explicitly calls C<CORE::exit> when
801it is done (it will raise an exception under other circumstances, which 801it is done (under other circumstances, such as when there is an I/O error
802might lead to the process not exiting on it's own). 802and there is outstanding data to write, it will log a fatal message via
803L<AnyEvent::Log>, also causing the program to exit).
803 804
804You can override this by specifying a function name to call via the C<done> 805You can override this by specifying a function name to call via the C<done>
805parameter instead. 806parameter instead.
806 807
807=back 808=back

Diff Legend

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