SignalRun Lastrequest-SignalRun Lastrequest-Emitted when a request is removed from session's queue,
indicating that session is done with it.
See Soup.Session::request-queued for a detailed description of
the message lifecycle within a session.
SignalDetailedActionRun FirstnotifyThe notify signal is emitted on an object when one of its properties has
its value set through g_object_set_property(), g_object_set(), et al.
Note that getting this signal doesn’t itself guarantee that the value of
the property has actually changed. When it is emitted is determined by the
derived GObject class. If the implementor did not create the property with
GObject.ParamFlags.EXPLICIT_NOTIFY, then any call to g_object_set_property() results
in ::notify being emitted, even if the new value is the same as the old.
If they did pass GObject.ParamFlags.EXPLICIT_NOTIFY, then this signal is emitted only
when they explicitly call g_object_notify() or g_object_notify_by_pspec(),
and common practice is to do that only when the value has actually changed.
This signal is typically used to obtain change notification for a
single property, by specifying the property name as a detail in the
g_signal_connect() call, like this:
g_signal_connect (text_view->buffer, "notify::paste-target-list",
G_CALLBACK (gtk_text_view_target_list_notify),
text_view)
It is important to note that you must use [canonical parameter names][class@GObject.ParamSpec#parameter-names] as detail strings for the notify signal.
Emitted when a request is queued on
session.When sending a request, first
Soup.Session::request-queuedis emitted, indicating that the session has become aware of the request.After a connection is available to send the request various Message signals are emitted as the message is processed. If the message is requeued, it will emit
Soup.Message::restarted, which will then be followed by other Message signals when the message is re-sent.Eventually, the message will emit
Soup.Message::finished. Normally, this signals the completion of message processing. However, it is possible that the application will requeue the message from the "finished" handler. In that case the process will loop back.Eventually, a message will reach "finished" and not be requeued. At that point, the session will emit
Soup.Session::request-unqueuedto indicate that it is done with the message.To sum up:
Soup.Session::request-queuedandSoup.Session::request-unqueuedare guaranteed to be emitted exactly once, butSoup.Message::finished(and all of the other Message signals) may be invoked multiple times for a given message.