view release on metacpan or  search on metacpan

README  view on Meta::CPAN

        indicate that it is pushing the filehandle onto the end of a queue.
        Hopefully it should remind you of the similarly named "push_write"
        method in AnyEvent::Handle.

    $passer->push_recv_fh($cb->($fh))
        In order to receive the filehandle, the receiving process calls
        "push_recv_fh" and passes it a callback that will be called once one
        is available. The filehandle will be the first argument to this
        callback.

        Note that you can add multiple callbacks with "push_recv_fh" to the
        input queue between returning to the main loop. The callbacks will
        be invoked in the same order that the filehandles are received
        (which is the same order that they were sent).

        This method is called "push_recv_fh" instead of, say, "recv_fh" to
        indicate that it is pushing a callback onto the end of a queue.
        Hopefully it should remind you of the similarly named "push_read"
        method in AnyEvent::Handle.

    AnyEvent::FDpasser::fdpasser_socketpair()
        This function returns two handles representing both ends of a

README.pod  view on Meta::CPAN

In any case, the C<push_send_fh> method will not block. If you wish to perform some action once the socket actually has been sent, you can pass a callback as the second argument to C<push_send_fh>. It will be invoked after the descriptor has been sen...

This method is called C<push_send_fh> instead of, say, C<send_fh> to indicate that it is pushing the filehandle onto the end of a queue. Hopefully it should remind you of the similarly named C<push_write> method in L<AnyEvent::Handle>.


=item $passer->push_recv_fh($cb->($fh))

In order to receive the filehandle, the receiving process calls C<push_recv_fh> and passes it a callback that will be called once one is available. The filehandle will be the first argument to this callback.

Note that you can add multiple callbacks with C<push_recv_fh> to the input queue between returning to the main loop. The callbacks will be invoked in the same order that the filehandles are received (which is the same order that they were sent).

This method is called C<push_recv_fh> instead of, say, C<recv_fh> to indicate that it is pushing a callback onto the end of a queue. Hopefully it should remind you of the similarly named C<push_read> method in L<AnyEvent::Handle>.



=item AnyEvent::FDpasser::fdpasser_socketpair()

This function returns two handles representing both ends of a connected socketpair. On BSD systems it uses C<socketpair(2)> and on SysV systems it uses C<pipe(2)>. Note that this function doesn't work on windows so it's not really useful as a fully-g...

=item $listener_fh = AnyEvent::FDpasser::fdpasser_server($path[, $backlog ])

lib/AnyEvent/FDpasser.pm  view on Meta::CPAN

In any case, the C<push_send_fh> method will not block. If you wish to perform some action once the socket actually has been sent, you can pass a callback as the second argument to C<push_send_fh>. It will be invoked after the descriptor has been sen...

This method is called C<push_send_fh> instead of, say, C<send_fh> to indicate that it is pushing the filehandle onto the end of a queue. Hopefully it should remind you of the similarly named C<push_write> method in L<AnyEvent::Handle>.


=item $passer->push_recv_fh($cb->($fh))

In order to receive the filehandle, the receiving process calls C<push_recv_fh> and passes it a callback that will be called once one is available. The filehandle will be the first argument to this callback.

Note that you can add multiple callbacks with C<push_recv_fh> to the input queue between returning to the main loop. The callbacks will be invoked in the same order that the filehandles are received (which is the same order that they were sent).

This method is called C<push_recv_fh> instead of, say, C<recv_fh> to indicate that it is pushing a callback onto the end of a queue. Hopefully it should remind you of the similarly named C<push_read> method in L<AnyEvent::Handle>.



=item AnyEvent::FDpasser::fdpasser_socketpair()

This function returns two handles representing both ends of a connected socketpair. On BSD systems it uses C<socketpair(2)> and on SysV systems it uses C<pipe(2)>. Note that this function doesn't work on windows so it's not really useful as a fully-g...

=item $listener_fh = AnyEvent::FDpasser::fdpasser_server($path[, $backlog ])