… | |
… | |
29 | hacking L<Net::DBus::Reactor> so that all dbus connections created after |
29 | hacking L<Net::DBus::Reactor> so that all dbus connections created after |
30 | loading this module will automatically be managed by this module. |
30 | loading this module will automatically be managed by this module. |
31 | |
31 | |
32 | Note that a) a lot inside Net::DBus is still blocking b) if you call a |
32 | Note that a) a lot inside Net::DBus is still blocking b) if you call a |
33 | method that blocks, you again block your process (basically anything |
33 | method that blocks, you again block your process (basically anything |
34 | but calls to the Net::DBus::Binding::Connection objects block, but |
34 | but calls to the Net::DBus::Binding::Connection objects block, but see |
35 | see Net::DBus::Annoation, specifically dbus_call_async) and c) this |
35 | Net::DBus::Annoation, specifically dbus_call_async) c) the underlying |
|
|
36 | libdbus is often blocking itself, even with infinite timeouts and d) this |
36 | module only implements the minimum API required to make Net::DBus work - |
37 | module only implements the minimum API required to make Net::DBus work - |
37 | Net::DBus unfortunately has no nice hooking API. |
38 | Net::DBus unfortunately has no nice hooking API. |
38 | |
39 | |
39 | However, unlike L<Net::DBus::Reactor>, this module should be fully |
40 | However, unlike L<Net::DBus::Reactor>, this module should be fully |
40 | non-blocking as long as you only use non-blocking APIs (Net::DBus::Reactor |
41 | non-blocking as long as you only use non-blocking APIs (Net::DBus::Reactor |
41 | blocks on writes). It should also be faster, but Net::DBus is such a |
42 | blocks on writes). It should also be faster, but Net::DBus is such a |
42 | morass os unneeded method calls that speed won't matter much... |
43 | morass so unneeded method calls that speed won't matter much... |
43 | |
44 | |
44 | =head2 EXAMPLE |
45 | =head2 EXAMPLE |
45 | |
46 | |
46 | Here is a simple example. Both work with AnyEvent::DBus and do the same |
47 | Here is a simple example. Both work with AnyEvent::DBus and do the same |
47 | thing, but only the second is actually non-blocking. |
48 | thing, but only the second is actually non-blocking. |
… | |
… | |
164 | $con->set_watch_callbacks (\&io_on, \&watch_off, \&io_toggle); |
165 | $con->set_watch_callbacks (\&io_on, \&watch_off, \&io_toggle); |
165 | # if $con->can ("set_watch_callbacks"); |
166 | # if $con->can ("set_watch_callbacks"); |
166 | |
167 | |
167 | $con->set_timeout_callbacks (\&timeout_on, \&watch_off, \&timeout_toggle); |
168 | $con->set_timeout_callbacks (\&timeout_on, \&watch_off, \&timeout_toggle); |
168 | # if $con->can ("set_timeout_callbacks"); |
169 | # if $con->can ("set_timeout_callbacks"); |
|
|
170 | |
|
|
171 | $con->dispatch; # for good measure |
169 | } |
172 | } |
170 | |
173 | |
171 | =head1 SEE ALSO |
174 | =head1 SEE ALSO |
172 | |
175 | |
173 | L<AnyEvent>, L<Net::DBus>. |
176 | L<AnyEvent>, L<Net::DBus>. |