*/ #include 'common-defs.h' /** * Define enumerations for the different signals that we can generate * (so that we can refer to them within the signals-array * using symbolic names). */ #include #include #include /* exit, EXIT_FAILURE */ #include /* daemon */ /* Pull symbolic constants that are shared (in this example) between the client and the server. Adding * timestamps to each trace message is left out (see gettimeofday() * system call for a simple solution). * * Demonstrates a simple implementation of 'tracing' as well (via the * NO_DAEMON define, as when built as non-daemonizing version, will * output information about what is happening and where. * Important things like object life-time management (freeing of * objects), sub-classing and GObject properties are not covered at * all. * * This program also might serve as an introduction into implementing * custom GType/GObjects, but it is not the primary purpose here. * * This program will pull the automatically generated D-Bus/GLib stub * code (which contains the marshaling code as well as a binding/call * table. In this * server, they're all present in this file. * * In more complicated code, the GObject definition, implementation * and D-Bus registration would all live in separate files. * * This maemo code example is licensed under a MIT-style license, * that can be found in the file called 'License' in the same * directory as this file.

** * This program implements a GObject for a simple class, then * registers the object on the D-Bus and starts serving requests. Glib-dbus-signals/value-dbus-interface.xml */ #define SIGNAL_CHANGED_VALUE1 'changed_value1' #define SIGNAL_CHANGED_VALUE2 'changed_value2' #define SIGNAL_OUTOFRANGE_VALUE1 'outofrange_value1' #define SIGNAL_OUTOFRANGE_VALUE2 'outofrange_value2' #endif These need to map into the D-Bus signal names. */ #define VALUE_SERVICE_INTERFACE '' /* Symbolic constants for the signal names to use with GLib. This must match the entry in the interface definition XML. */ #define VALUE_SERVICE_OBJECT_PATH '/GlobalValue' /* And we're interested in using it through this interface. */ #define VALUE_SERVICE_NAME '_ex' /* Object path to the provided object. * * To re-iterate: You could just as easily use strings in both client * and server, and that would be the more common way.

Normally this kind of information would be part of the * object usage documentation, but in this example we take the easy * way out. * * This file includes the common symbolic defines for both client and * the server. ** * This maemo code example is licensed under a MIT-style license, * that can be found in the file called 'License' in the same * directory as this file. glib-dbus-signals/value-dbus-interface.xml.

APPENDIX E - Source code for the GLib/D-Bus signal example Chapter contents:

Dbus source code