diff options
| author | Jens Georg <mail@jensge.org> | 2014-05-10 14:04:46 +0200 |
|---|---|---|
| committer | Jens Georg <mail@jensge.org> | 2014-05-10 14:05:41 +0200 |
| commit | fde1264daa567b0978c8ca56f829de022f77dc2c (patch) | |
| tree | ed0a0c39d73cb068dfa58e30e236c9f2e00f0964 | |
| parent | e59250a15d30bd0c1fefbe7934cf2b4b9f20aab9 (diff) | |
| download | gupnp-fde1264daa567b0978c8ca56f829de022f77dc2c.tar.gz | |
doc: Remove reference to general signal handling
Signed-off-by: Jens Georg <mail@jensge.org>
https://bugzilla.gnome.org/show_bug.cgi?id=729827
| -rw-r--r-- | doc/server-tutorial.xml | 12 |
1 files changed, 4 insertions, 8 deletions
diff --git a/doc/server-tutorial.xml b/doc/server-tutorial.xml index 8f03295..65a33a9 100644 --- a/doc/server-tutorial.xml +++ b/doc/server-tutorial.xml @@ -182,14 +182,10 @@ service = gupnp_device_info_get_service value of the variable. </para> <para> - There are two approaches that clients can take to handle these signals. - They can either connect a single handler to #GUPnPService::action-invoked - or #GUPnPService::query-variable and examine the arguments to decide what - action to take. Alternatively, handlers can be targetted at specific - actions or variables by using the <firstterm>signal detail</firstterm> - when connecting. For example, this causes - <function>on_get_status_action</function> to be called when the - <function>GetStatus</function> action is invoked: + Handlers should be targetted at specific actions or variables by using + the <firstterm>signal detail</firstterm> when connecting. For example, + this causes <function>on_get_status_action</function> to be called when + the <function>GetStatus</function> action is invoked: </para> <programlisting>static void on_get_status_action (GUPnPService *service, GUPnPServiceAction *action, gpointer user_data); … |