doc: Add status_code to Completed signal(s) 76/273776/1
authorKarol Lewandowski <k.lewandowsk@samsung.com>
Wed, 13 Apr 2022 13:27:25 +0000 (15:27 +0200)
committerKarol Lewandowski <k.lewandowsk@samsung.com>
Wed, 13 Apr 2022 13:27:25 +0000 (15:27 +0200)
It seems we have not provided any means to return if operations
have succeeded or not.

This commit introduces `status_code` field, which allows service
to return status, if/as needed.

Surely, adding signals <Operation>Failed would be better from
design perspective, and might be considered in future if time
allows (dbus signals are private interface and subject to change
without notice).

Change-Id: Ib77681597c6633c62ae0936040f26633a9bdad05

doc/sessiond-dbus-interface.md

index b913773..f347209 100644 (file)
@@ -134,24 +134,27 @@ In case of an error, methods return a DBus error.
         objpath: /org/tizen/sessiond
         interface: org.tizen.sessiond.subsession.Manager
         member: AddUserCompleted
-        parameters: (ii)
+        parameters: (iii)
             session_uid <int32>
             subsession_id <int32>
+            status_code <int32>
 
 5. On user removal completed:
 
         objpath: /org/tizen/sessiond
         interface: org.tizen.sessiond.subsession.Manager
         member: RemoveUserCompleted
-        parameters: (ii)
+        parameters: (iii)
             session_uid <int32>
             subsession_id <int32>
+            status_code <int32>
 
 6. On user switch completed:
 
         objpath: /org/tizen/sessiond
         interface: org.tizen.sessiond.subsession.Manager
         member: SwitchUserCompleted
-        parameters: (ix)
+        parameters: (ixi)
             session_uid <int32>
             switch_id <int64>
+            status_code <int32>