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

Comparing AnyEvent-FCP/FCP.pm (file contents):
Revision 1.24 by root, Sun Jun 12 04:44:05 2016 UTC vs.
Revision 1.25 by root, Wed Jun 15 09:20:42 2016 UTC

 =item on_error => $callback->($fcp, $message)
 Invoked on any (fatal) errors, such as unexpected connection close. The
 callback receives the FCP object and a textual error message.
-=item on_failure => $callback->($fcp, $type, $backtrace, $args, $error)
+=item on_failure => $callback->($fcp, $type, $args, $backtrace, $error)
 Invoked when an FCP request fails that didn't have a failure callback. See
 L<FCP REQUESTS> for details.
 =back
 This is a popular choice, but it makes handling errors hard - make sure
 you never generate protocol errors!
 In the failure case, if an C<on_failure> hook exists, it will be invoked
-with the FCP object, the request type (the name of the method), a
+with the FCP object, the request type (the name of the method, an arrayref
-(textual) backtrace as generated by C<Carp::longmess>, and arrayref
-containing the arguments from the original request invocation and the
+containing the arguments from the original request invocation, a (textual)
-error object from the server, in this order, e.g.:
+backtrace as generated by C<Carp::longmess>, and the error object from the
+server, in this order, e.g.:
    on_failure => sub {
-      my ($fcp, $request_type, $backtrace, $orig_args, $error_object) = @_;
+      my ($fcp, $request_type, $orig_args, $backtrace, $error_object) = @_;
       warn "FCP failure ($type), $error_object->{code_description} ($error_object->{extra_description})$backtrace";
       exit 1;
    },

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