From 13736d0ced2d6d873c1cac5ac840e58dfce83f64 Mon Sep 17 00:00:00 2001 From: Peter Hutterer Date: Wed, 11 Oct 2017 14:46:50 +1000 Subject: [PATCH] DBus: thighten the definition of the 'Id' for a device We can't guarantee it's a sysname even though that is what we use for evdev devices. Future devices may just be some custom-assigned name for a remote dbus API Signed-off-by: Peter Hutterer --- DBusInterface.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/DBusInterface.md b/DBusInterface.md index c1a93bfd..2eb87432 100644 --- a/DBusInterface.md +++ b/DBusInterface.md @@ -60,7 +60,9 @@ known to ratbagd. - type: `s`, read-only, constant An ID describing this device. This ID should not be used for presentation to -the user. +the user. This ID is unique for the device for the lifetime of the device +but may be recycled when the device is removed. No guarantee is given for +the content of the ID, the client should treat it as an opaque string. #### `Description` - type: `s`, read-only, constant