From: Martin Willi <martin@revosec.ch>
Date: Thu, 2 May 2013 09:22:51 +0000 (+0200)
Subject: xpc: add a description of the basic XPC protocol to README
X-Git-Tag: 5.1.0rc1~25^2~15
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=dcf8a3c78b8b1851acf68b359e24a346ca4ed17d;p=thirdparty%2Fstrongswan.git

xpc: add a description of the basic XPC protocol to README
---

diff --git a/src/frontends/osx/README.md b/src/frontends/osx/README.md
index 62a0b2e0d6..39b5c7349c 100644
--- a/src/frontends/osx/README.md
+++ b/src/frontends/osx/README.md
@@ -38,4 +38,51 @@ any non OS X dependencies.
 
 Both charon-xpc and the App must be code-signed to allow the installation of
 the privileged helper. git-grep for "Joe Developer" to change the signing
-identity.
\ No newline at end of file
+identity.
+
+## XPC application protocol ##
+
+charon-xpc provides a Mach service under the name _org.strongswan.charon-xpc_.
+Clients can connect to this service to control the daemon. All messages
+on all connections use the following string dictionary keys/values:
+
+* _type_: XPC message type, currently either
+ * _rpc_ for a remote procedure call, expects a response
+ * _event_ for application specific event messages
+* _rpc_: defines the name of the RPC function to call (for _type_ = _rpc_)
+* _event_: defines a name for the event (for _type_ = _event_)
+
+Additional arguments and return values are specified by the call and can have
+any type. Keys are directly attached to the message dictionary.
+
+On the Mach service connection, the following RPC messages are currently
+defined:
+
+* string version = get_version()
+  * _version_: strongSwan version of charon-xpc
+* bool success = start_connection(string name, string host, string id,
+                                  endpoint channel)
+  * _success_: TRUE if initiation started successfully
+  * _name_: connection name to initiate
+  * _host_: server hostname (and identity)
+  * _id_: client identity to use
+  * _channel_: XPC endpoint for this connection
+
+The start_connection() RPC returns just after the initation of the call and
+does not wait for the connection to establish. Nonetheless does it have a
+return value to indicate if connection initiation could be triggered.
+
+The App passes an (anonymous) XPC endpoint to start_connection(). If the call
+succeeds, charon-xpc connects to this endpoint to establish a channel used for
+this specific IKE connection.
+
+On this channel, the following RPC calls are currently defined from charon-xpc
+to the App:
+
+* string password = get_password(string username)
+  * _password_: user password returned
+  * _username_: username to query a password for
+
+The following events are currently defined from charon-xpc to the App:
+* _up_: connection has been established
+* _down_: connection has been closed or failed to establish