/usr/share/help/de/gnome-devel-demos/custom-gsource.c.page is in gnome-devel-docs 3.28.0-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 | <?xml version="1.0" encoding="utf-8"?>
<page xmlns="http://projectmallard.org/1.0/" xmlns:its="http://www.w3.org/2005/11/its" xmlns:xi="http://www.w3.org/2003/XInclude" type="guide" style="task" id="custom-gsource.c" xml:lang="de">
<info>
<link type="guide" xref="c#examples"/>
<credit type="author copyright">
<name>Philip Withnall</name>
<email its:translate="no">philip.withnall@collabora.co.uk</email>
<years>2015</years>
</credit>
<include xmlns="http://www.w3.org/2001/XInclude" href="legal.xml"/>
<desc>
Tutorial for writing a custom <code>GSource</code> implementation
</desc>
<mal:credit xmlns:mal="http://projectmallard.org/1.0/" type="translator copyright">
<mal:name>Mario Blättermann</mal:name>
<mal:email>mario.blaettermann@gmail.com</mal:email>
<mal:years>2011, 2013</mal:years>
</mal:credit>
</info>
<title>Custom GSources</title>
<synopsis>
<title>Zusammenfassung</title>
<p>
This article is a tutorial on creating a custom <code>GSource</code>. For
the reference documentation, see the
<link href="https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html#GSource">GLib
API reference</link>.
</p>
</synopsis>
<section id="what-is-gsource">
<title>Was ist <code>GSource</code>?</title>
<p>
A <link href="https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html#GSource"><code>GSource</code></link>
is an expected event with an associated callback function which will be
invoked when that event is received. An event could be a timeout or data
being received on a socket, for example.
</p>
<p>
GLib contains various types of <code>GSource</code>, but also allows
applications to define their own, allowing custom events to be integrated
into the main loop.
</p>
<p>
The structure of a <code>GSource</code> and its virtual functions are
documented in detail in the
<link href="https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html#GSourceFuncs">GLib
API reference</link>.
</p>
</section>
<section id="queue-source">
<title>A Message Queue Source</title>
<p>
As a running example, a message queue source will be used which dispatches
its callback whenever a message is enqueued to a queue internal to the
source (potentially from another thread).
</p>
<p>
This type of source is useful for efficiently transferring large numbers
of messages between main contexts. The alternative is transferring each
message as a separate idle <code>GSource</code> using
<code>g_source_attach()</code>. For large numbers of messages, this means
a lot of allocations and frees of <code>GSource</code>s.
</p>
<section id="gsource-structure">
<title>Struktur</title>
<p>
Firstly, a structure for the source needs to be declared. This must
contain a <code>GSource</code> as its parent, followed by the private
fields for the source: the queue and a function to call to free each
message once finished with.
</p>
<code mime="text/x-csrc">
typedef struct {
GSource parent;
GAsyncQueue *queue; /* owned */
GDestroyNotify destroy_message;
} MessageQueueSource;</code>
</section>
<section id="prepare-function">
<title>Prepare-Funktion</title>
<p>
Next, the prepare function for the source must be defined. This determines
whether the source is ready to be dispatched. As this source is using an
in-memory queue, this can be determined by checking the queue’s length: if
there are elements in the queue, the source can be dispatched to handle
them.
</p>
<code mime="text/x-csrc">
return (g_async_queue_length (message_queue_source->queue) > 0);</code>
</section>
<section id="check-function">
<title>Check-Funktion</title>
<p>
As this source has no file descriptors, the prepare and check functions
essentially have the same job, so a check function is not needed.
Setting the field to <code>NULL</code> in <code>GSourceFuncs</code>
bypasses the check function for this source type.
</p>
</section>
<section id="dispatch-function">
<title>Dispatch-Funktion</title>
<p>
For this source, the dispatch function is where the complexity lies. It
needs to dequeue a message from the queue, then pass that message to the
<code>GSource</code>’s callback function. No messages may be queued: even
through the prepare function returned true, another source wrapping the
same queue may have been dispatched in the mean time and taken the final
message from the queue. Further, if no callback has been set for the
<code>GSource</code> (which is allowed), the message must be destroyed and
silently dropped.
</p>
<p>
If both a message and callback are set, the callback can be invoked on the
message and its return value propagated as the return value of the
dispatch function. This is <code>FALSE</code> to destroy the
<code>GSource</code> and <code>TRUE</code> to keep it alive, just as for
<code>GSourceFunc</code> — these semantics are the same for all dispatch
function implementations.
</p>
<code mime="text/x-csrc">
/* Pop a message off the queue. */
message = g_async_queue_try_pop (message_queue_source->queue);
/* If there was no message, bail. */
if (message == NULL)
{
/* Keep the source around to handle the next message. */
return TRUE;
}
/* @func may be %NULL if no callback was specified.
* If so, drop the message. */
if (func == NULL)
{
if (message_queue_source->destroy_message != NULL)
{
message_queue_source->destroy_message (message);
}
/* Keep the source around to consume the next message. */
return TRUE;
}
return func (message, user_data);</code>
</section>
<section id="callback">
<title>Callback-Funktionen</title>
<p>
The callback from a <code>GSource</code> does not have to have type
<code>GSourceFunc</code>. It can be whatever function type is called in
the source’s dispatch function, as long as that type is sufficiently
documented.
</p>
<p>
Normally, <code>g_source_set_callback()</code> is used to set the
callback function for a source instance. With its
<code>GDestroyNotify</code>, a strong reference can be held to keep an
object alive while the source is still alive:
</p>
<code mime="text/x-csrc">
g_source_set_callback (source, callback_func,
g_object_ref (object_to_strong_ref),
(GDestroyNotify) g_object_unref);</code>
<p>
However, <code>GSource</code> has a layer of indirection for retrieving
this callback, exposed as <code>g_source_set_callback_indirect()</code>.
This allows GObject to set a <code>GClosure</code> as the callback for a
source, which allows for sources which are automatically destroyed when
an object is finalized — a <em>weak</em> reference, in contrast to the
<em>strong</em> reference above:
</p>
<code mime="text/x-csrc">
g_source_set_closure (source,
g_cclosure_new_object (callback_func,
object_to_weak_ref));</code>
<p>
It also allows for a generic, closure-based ‘dummy’ callback, which can
be used when a source needs to exist but no action needs to be performed
in its callback:
</p>
<code mime="text/x-csrc">
g_source_set_dummy_callback (source);</code>
</section>
<section id="constructor">
<title>Constructor</title>
<p>
Finally, the <code>GSourceFuncs</code> definition of the
<code>GSource</code> can be written, alongside a construction function.
It is typical practice to expose new source types simply as
<code>GSource</code>s, not as the subtype structure; so the constructor
returns a <code>GSource*</code>.
</p>
<p>
The example constructor here also demonstrates use of a child source to
support cancellation conveniently. If the <code>GCancellable</code> is
cancelled, the application’s callback will be dispatched and can check
for cancellation. (The application code will need to make a pointer to
the <code>GCancellable</code> available to its callback, as a field of the
callback’s user data set in <code>g_source_set_callback()</code>).
</p>
<code mime="text/x-csrc">
GSource *
message_queue_source_new (GAsyncQueue *queue,
GDestroyNotify destroy_message,
GCancellable *cancellable)
{
GSource *source; /* alias of @message_queue_source */
MessageQueueSource *message_queue_source; /* alias of @source */
g_return_val_if_fail (queue != NULL, NULL);
g_return_val_if_fail (cancellable == NULL ||
G_IS_CANCELLABLE (cancellable), NULL);
source = g_source_new (&message_queue_source_funcs,
sizeof (MessageQueueSource));
message_queue_source = (MessageQueueSource *) source;
/* The caller can overwrite this name with something more useful later. */
g_source_set_name (source, "MessageQueueSource");
message_queue_source->queue = g_async_queue_ref (queue);
message_queue_source->destroy_message = destroy_message;
/* Add a cancellable source. */
if (cancellable != NULL)
{
GSource *cancellable_source;
cancellable_source = g_cancellable_source_new (cancellable);
g_source_set_dummy_callback (cancellable_source);
g_source_add_child_source (source, cancellable_source);
g_source_unref (cancellable_source);
}
return source;
}</code>
</section>
</section>
<section id="full-listing">
<title>Vollständiges Beispiel</title>
<listing>
<title>Vollständiger Beispielcode</title>
<code mime="text/x-csrc">/**
* MessageQueueSource:
*
* This is a #GSource which wraps a #GAsyncQueue and is dispatched whenever a
* message can be pulled off the queue. Messages can be enqueued from any
* thread.
*
* The callbacks dispatched by a #MessageQueueSource have type
* #MessageQueueSourceFunc.
*
* #MessageQueueSource supports adding a #GCancellable child source which will
* additionally dispatch if a provided #GCancellable is cancelled.
*/
typedef struct {
GSource parent;
GAsyncQueue *queue; /* owned */
GDestroyNotify destroy_message;
} MessageQueueSource;
/**
* MessageQueueSourceFunc:
* @message: (transfer full) (nullable): message pulled off the queue
* @user_data: user data provided to g_source_set_callback()
*
* Callback function type for #MessageQueueSource.
*/
typedef gboolean (*MessageQueueSourceFunc) (gpointer message,
gpointer user_data);
static gboolean
message_queue_source_prepare (GSource *source,
gint *timeout_)
{
MessageQueueSource *message_queue_source = (MessageQueueSource *) source;
return (g_async_queue_length (message_queue_source->queue) > 0);
}
static gboolean
message_queue_source_dispatch (GSource *source,
GSourceFunc callback,
gpointer user_data)
{
MessageQueueSource *message_queue_source = (MessageQueueSource *) source;
gpointer message;
MessageQueueSourceFunc func = (MessageQueueSourceFunc) callback;
/* Pop a message off the queue. */
message = g_async_queue_try_pop (message_queue_source->queue);
/* If there was no message, bail. */
if (message == NULL)
{
/* Keep the source around to handle the next message. */
return TRUE;
}
/* @func may be %NULL if no callback was specified.
* If so, drop the message. */
if (func == NULL)
{
if (message_queue_source->destroy_message != NULL)
{
message_queue_source->destroy_message (message);
}
/* Keep the source around to consume the next message. */
return TRUE;
}
return func (message, user_data);
}
static void
message_queue_source_finalize (GSource *source)
{
MessageQueueSource *message_queue_source = (MessageQueueSource *) source;
g_async_queue_unref (message_queue_source->queue);
}
static gboolean
message_queue_source_closure_callback (gpointer message,
gpointer user_data)
{
GClosure *closure = user_data;
GValue param_value = G_VALUE_INIT;
GValue result_value = G_VALUE_INIT;
gboolean retval;
/* The invoked function is responsible for freeing @message. */
g_value_init (&result_value, G_TYPE_BOOLEAN);
g_value_init (&param_value, G_TYPE_POINTER);
g_value_set_pointer (&param_value, message);
g_closure_invoke (closure, &result_value, 1, &param_value, NULL);
retval = g_value_get_boolean (&result_value);
g_value_unset (&param_value);
g_value_unset (&result_value);
return retval;
}
static GSourceFuncs message_queue_source_funcs =
{
message_queue_source_prepare,
NULL, /* check */
message_queue_source_dispatch,
message_queue_source_finalize,
(GSourceFunc) message_queue_source_closure_callback,
NULL,
};
/**
* message_queue_source_new:
* @queue: the queue to check
* @destroy_message: (nullable): function to free a message, or %NULL
* @cancellable: (nullable): a #GCancellable, or %NULL
*
* Create a new #MessageQueueSource, a type of #GSource which dispatches for
* each message queued to it.
*
* If a callback function of type #MessageQueueSourceFunc is connected to the
* returned #GSource using g_source_set_callback(), it will be invoked for each
* message, with the message passed as its first argument. It is responsible for
* freeing the message. If no callback is set, messages are automatically freed
* as they are queued.
*
* Returns: (transfer full): a new #MessageQueueSource
*/
GSource *
message_queue_source_new (GAsyncQueue *queue,
GDestroyNotify destroy_message,
GCancellable *cancellable)
{
GSource *source; /* alias of @message_queue_source */
MessageQueueSource *message_queue_source; /* alias of @source */
g_return_val_if_fail (queue != NULL, NULL);
g_return_val_if_fail (cancellable == NULL ||
G_IS_CANCELLABLE (cancellable), NULL);
source = g_source_new (&message_queue_source_funcs,
sizeof (MessageQueueSource));
message_queue_source = (MessageQueueSource *) source;
/* The caller can overwrite this name with something more useful later. */
g_source_set_name (source, "MessageQueueSource");
message_queue_source->queue = g_async_queue_ref (queue);
message_queue_source->destroy_message = destroy_message;
/* Add a cancellable source. */
if (cancellable != NULL)
{
GSource *cancellable_source;
cancellable_source = g_cancellable_source_new (cancellable);
g_source_set_dummy_callback (cancellable_source);
g_source_add_child_source (source, cancellable_source);
g_source_unref (cancellable_source);
}
return source;
}
</code>
</listing>
</section>
<section id="further-examples">
<title>Weitere Beispiele</title>
<p>
Sources can be more complex than the example given above. In
<link href="http://nice.freedesktop.org/">libnice</link>, a custom
<code>GSource</code> is needed to poll a set of sockets which changes
dynamically. The implementation is given as <code>ComponentSource</code>
in <link href="http://cgit.freedesktop.org/libnice/libnice/tree/agent/component.c#n941">component.c</link>
and demonstrates a more complex use of the prepare function.
</p>
<p>
Another example is a custom source to interface GnuTLS with GLib in its
<code>GTlsConnection</code> implementation.
<link href="https://git.gnome.org/browse/glib-networking/tree/tls/gnutls/gtlsconnection-gnutls.c#n871"><code>GTlsConnectionGnutlsSource</code></link>
synchronizes the main thread and a TLS worker thread which performs the
blocking TLS operations.
</p>
</section>
</page>
|