Re: [PATCH BLUEZ 0/4] Modify Health profile signals for ObjectManager

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Dohyun,

On Sun, Jul 19, 2015 at 6:31 PM, Dohyun Pyun <re20sfree@xxxxxxxxx> wrote:
> From: DoHyun Pyun <dh79.pyun@xxxxxxxxxxx>
>
> Since BlueZ has ObjectManager interface, ChannelConnected and ChannelDeleted
> Signals of HealthDevice interface was not available. ObjectManager reports the
> HealthChannel D-Bus interface when g_dbus_emit_signal function is called,
> and generates "InterfaceAdded" signal. But ChannelConnected and ChannelDeleted
> Siganls was not generated. If health-api document contains these signals,
> application or service using Bluez Dbus API will get the unexpected result.
>
> If we just remove g_dbus_emit_signal for ChannelConnected and ChannelDeleted,
> InterfaceAdded signal will not sent. Because InterfaceAdded signal is pending
> before sending a dbus signal. These patches include new property in HealthChannel
> interfacem, and this PropertiesChanged signal can be used to replace the previous
> ChannelConnected and ChannelDeleted signals.

Seems like a good idea, but from the logs it looks like the channel
lifetime is tied with the connection in that case
InterfacesAdded/InterfacesRemoved can be used directly instead of
having another property or Im missing something?


-- 
Luiz Augusto von Dentz
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux