| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Adapt to the new DBus.Properties and cleanup the format used in this
documentation to be similar to the other profiles.
|
| | |
|
| | |
|
| |
|
|
|
| |
Channel path skeleton is fixed in documentation, in order to
reflect atual implementation.
|
| |
|
|
|
|
|
|
|
|
|
| |
This patch adds the Application property to HealthChannel, which
allows to unambiguously relate a channel to an application.
This property is useful when there are several processes interested
in accepting HealthChannels but device address is not sufficient
criteria to engage upon, or ignore, the ChannelConnected signal.
Having the application path allows to determine role and data type,
in the context of the process that has created that application.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Connections are made directly to a device and bluetoothd daemon
guess the PSM connection and the MDEPID based on the data get
from the SDP record.
Also a property that indicates the first realiable channel is
added to the HealthDevice object.
|
| |
|
|
|
|
|
|
| |
Create/Destroy makes more sense since the application is created on the
bluetoothd side whereas what's really registered is an agent on the
caller side. This way the call is similar to e.g. CreatePairedDevice,
and so the parameter order should also be config first and then the
agent.
|
| |
|
