Hi folks,<br>
<br>
Suppose that I need work with the following paths:<br>
<br>
* Main path<br>
path: "/org/bluez/Manager" (always active)<br>
<br>
* Device dependent Service<br>
path: "/org/bluez/Manager/default/controller" (default HCI services)<br>
path: "/org/bluez/Manager/hci0/controller" (HCI services)<br>
path: "/org/bluez/Manager/hci1/controller" (HCI services)<br>
path: "/org/bluez/Manager/default/pan" (default PAN services)<br>
path: "/org/bluez/Manager/hci0/pan" (PAN services)<br>
path: "/org/bluez/Manager/hci1/pan" (PAN services)<br>
path: "/org/bluez/Manager/default/serial" (default RFCOMM services)<br>
path: "/org/bluez/Manager/hci0/serial" (RFCOMM services)<br>
path: "/org/bluez/Manager/hci1/serial" (RFCOMM services)<br>
path: "/org/bluez/Manager/defaulti/services" (default SDP publish/search)<br>
path: "/org/bluez/Manager/hci0/services" (services SDP publish/search)<br>
path: "/org/bluez/Manager/hci1/services" (services SDP publish/search)<br>
<br>
When an adapter is detached the paths related to this adapter must unregistered. If I use the function <br>
dbus_connection_register_object_path I will not be able to handle the message in the "main path" and<br>
the clients will receive an unknown service. However if I use dbus_connection_register_fallback, messages<br>
sent to child paths will the catched by the "main path" if the child path was unregistered.<br>
<br>
My question is: how work properly with fallback register? Which function should I use for child path(normal or fallback)? <br>
What are the overheads of working with this structure?<br>
<br>
I checked the HAL code and noticed that there is only one registering call, how paths are registered for each device attached?<br>
dbus_connection_register_fallback (new_connection,<br>
"/org/freedesktop",<br>
&vtable,<br>
NULL);<br>
<br>
<br>
Regards,<br>
Claudio.<br>-- <br>---------------------------------------------------------<br>Claudio Takahasi<br>Nokia's Institute of Technology - INdT<br><a href="mailto:claudio.takahasi@indt.org.br">claudio.takahasi@indt.org.br</a>
<br>