view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

        - log any errors via AE::log fatal instead of die'ing in the
          async backend.

1.1   Sun Apr 28 15:48:17 CEST 2013
	- add support for the AnyEvent::Fork::Remote API.
        - switch to an ABI-independent protocol.
	- emit clearer diagnostic for some broken cpan-testers setups.

0.2   Sun Apr 21 14:26:16 CEST 2013
        - do not create a watcher when shutting down the object, shut down
          directly, to work around perl global destruction bugs.
        - expliticly call exit in child server - not elegant, but
          doesn't disturb any sane perl, and helps broken win32 perls
          to clean up.

0.1   Thu Apr 18 15:29:48 CEST 2013
	- first release.

0.00  Tue Apr 16 21:40:55 CEST 2013
	- post planning, pre writing.

README  view on Meta::CPAN

            evaluated: the first receives a list of perl values and must
            return an octet string. The second receives the octet string and
            must return the original list of values.

            If you need an external module for serialisation, then you can
            either pre-load it into your AnyEvent::Fork process, or you can
            add a "use" or "require" statement into the serialiser string.
            Or both.

            Here are some examples - all of them are also available as
            global variables that make them easier to use.

            $AnyEvent::Fork::RPC::STRING_SERIALISER - octet strings only
                This serialiser (currently the default) concatenates
                length-prefixes octet strings, and is the default. That
                means you can only pass (and return) strings containing
                character codes 0-255.

                The main advantages of this serialiser are the high speed
                and that it doesn't need another module. The main
                disadvantage is that you are very limited in what you can

RPC.pm  view on Meta::CPAN

For more complicated use cases, you can provide your own freeze and thaw
functions, by specifying a string with perl source code. It's supposed to
return two code references when evaluated: the first receives a list of
perl values and must return an octet string. The second receives the octet
string and must return the original list of values.

If you need an external module for serialisation, then you can either
pre-load it into your L<AnyEvent::Fork> process, or you can add a C<use>
or C<require> statement into the serialiser string. Or both.

Here are some examples - all of them are also available as global
variables that make them easier to use.

=over 4

=item C<$AnyEvent::Fork::RPC::STRING_SERIALISER> - octet strings only

This serialiser (currently the default) concatenates length-prefixes octet
strings, and is the default. That means you can only pass (and return)
strings containing character codes 0-255.