Hi Luiz,
> On Mon, Apr 27, 2015 at 6:14 AM, Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx> wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx>
>
> This adds Flags property to GattDescriptor so the server can define
> permissions and authentication requirements for descriptors.
> ---
> doc/gatt-api.txt | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/doc/gatt-api.txt b/doc/gatt-api.txt
> index 8db35f2..8459430 100644
> --- a/doc/gatt-api.txt
> +++ b/doc/gatt-api.txt
> @@ -210,6 +210,20 @@ Properties string UUID [read-only]
> gets updated only after a successful read request, upon
> which a PropertiesChanged signal will be emitted.
>
> + array{string} Flags [read-only]
> +
> + Defines how the descriptor value can be used.
> +
> + Possible values:
> +
> + "read"
> + "write-without-response"
> + "write"
> + "authenticated-signed-writes"
These 4 above are defined as characteristic properties in the CS, so
I'm not sure why they would be in a descriptor. The point of these
properties (as defined by the Core Spec) is not to communicate
attribute permissions but to tell the remote end what procedures a
characteristic supports in general. So there's no point of including
these in the descriptor as there is no way to communicate these over
ATT (whereas these are returned in a characteristic declaration and
extended properties descriptor value for characteristics). So maybe
just keep read/write for the basic permissions.
> + "encrypt-read"
> + "encrypt-write"
> + "encrypt-authenticated-read"
> + "encrypt-authenticated-write"
>
> Profile hierarcy
> ================
> --
> 2.1.0
>
> --
> 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
Thanks,
Arman
--
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
