X-Git-Url: https://gerrit.automotivelinux.org/gerrit/gitweb?p=src%2Fapp-framework-binder.git;a=blobdiff_plain;f=memo-supervisor.txt;h=f38c05d8792c8ec41afd61e160342a8422971808;hp=13e9d1d27770bd6f17a12b06e66cebb316713ba9;hb=ca0f859d96599c8ae295c85f825030c891969de1;hpb=8dc14014ad83952343d2473140103650555d5ea2

diff --git a/memo-supervisor.txt b/memo-supervisor.txt
index 13e9d1d2..f38c05d8 100644
--- a/memo-supervisor.txt
+++ b/memo-supervisor.txt
@@ -2,7 +2,7 @@
 Run the supervisor on the target for the public IP:
 ---------------------------------------------------
 
-	# afs-supervisor --port 1619 --token HELLO 
+	# afs-supervisor --port 1619 --token HELLO
 
 Run the client
 --------------
@@ -49,20 +49,20 @@ verbs that can be run, all are of the API 'supervisor':
 
 		execute the API/VERB(ARGS) for the daemon of pid X
 
-		usefull for (s/g)etting monitor info. ex: monitor/get({"apis":true})
+		useful for (s/g)etting monitor info. ex: monitor/get({"apis":true})
 
 		bound to the current client session (to be checked: usurpation of session?)
 
 	- trace         {"pid":X, ...}
 
-		like monitor/trace but not bound to session (in the future monitor/trace 
+		like monitor/trace but not bound to session (in the future monitor/trace
 		will be bound to sessions)
 
 		allows to trace specific session or any session
 
 		the pid isn't returned in the event (not sure to want it but open...)
 
-		use "name" and "tag" feature of "trace" to discrimate events on the client side.
+		use "name" and "tag" feature of "trace" to discriminate events on the client side.
 
 Examples of dialog:
 -------------------
@@ -282,3 +282,14 @@ ON-EVENT supervisor/trace:
 }
 
 
+Usefull commands:
+-----------------
+
+  TARGET=...
+
+  afb-client-demo -H ws://$TARGET:1619/api?token=HELLO\&uuid=HELLO supervisor list
+
+  afb-client-demo -H ws://$TARGET:1619/api?token=HELLO\&uuid=HELLO config '{"pid":XXXX}'
+
+  
+