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

Comparing AnyEvent-MPV/MPV.pm (file contents):
Revision 1.13 by root, Mon Mar 20 14:42:40 2023 UTC vs.
Revision 1.15 by root, Wed Mar 22 01:00:36 2023 UTC

 As a rule of thumb, all data you pass to this module to be sent to F<mpv>
 is expected to be in unicode. To pass something that isn't, you need to
 escape it using C<escape_binary>.
-Data received from C<$mpv>, however, is I<not> decoded to unicode, as data
+Data received from F<mpv>, however, is I<not> decoded to unicode, as data
 returned by F<mpv> is not generally encoded in unicode, and the encoding
 is usually unspecified. So if you receive data and expect it to be in
 unicode, you need to first decode it from UTF-8, but note that this might
 fail. This is not a limitation of this module - F<mpv> simply does not
 specify nor guarantee a specific encoding, or any encoding at all, in its
 You can register multiple handlers for the same event, and this method
 does not interfere with the C<on_event> mechanism. That is, you can
 completely ignore this method and handle events in a C<on_event> handler,
 or mix both approaches as you see fit.
+Note that unlike commands, event handlers are registered immediately, that
+is, you can issue a command, then register an event handler and then get
+an event for this handler I<before> the command is even sent to F<mpv>. If
+this kind of race is an issue, you can issue a dummy command such as
+C<get_version> and register the handler when the reply is received.
 =cut
 sub AnyEvent::MPV::Unevent::DESTROY {
    my ($evtcb, $event, $evtid) = @{$_[0]};
    delete $evtcb->{$event}{$evtid};

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