connectRequestQueued

Emitted when a request is queued on @session.

When sending a request, first signal@Session::request-queued is emitted, indicating that the session has become aware of the request.

After a connection is available to send the request various class@Message signals are emitted as the message is processed. If the message is requeued, it will emit signal@Message::restarted, which will then be followed by other class@Message signals when the message is re-sent.

Eventually, the message will emit signal@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 signal@Session::request-unqueued to indicate that it is done with the message.

To sum up: signal@Session::request-queued and signal@Session::request-unqueued are guaranteed to be emitted exactly once, but signal@Message::finished (and all of the other class@Message signals) may be invoked multiple times for a given message.

Parameters