Synchronous HTTP requests and QEventLoop

[wysota]

Question: is there a nicer way to achieve this?

Apart from wrapping it all in a single call, no.

Another question: is it possible to create an event loop that allows you to manually post events to it?

You don't post events to event loops but rather to objects. QEventLoop is such an object too of course but I can't think of a use case where you'd want to post an event to an event loop object.

[squidge]

I can't think of a way thats nicer from what you want to do.

QNetworkAccessManager was designed to be asynchronous. Why anyone would want a synchronous version is a little odd to me, but to each there own.

[ChrisW67]

Here is an example that uses a synchronous request.

A system can issue requests to services X, Y, and Z over the network at user request. If this is the first time in a program run that an operation is requested then the system must first request a "login" (L) of the user with the service provider before completing the operation X, Y, or Z. L must complete entirely before operation X, Y, or Z is continued because a cookie returned by L must be available during X, Y, or Z. If the operation X, Y, or Z fails because the cookie has expired or been otherwise rejected by the service provider (perhaps they reboot a server) then the L process must be completed followed by a repeated X, Y, or Z.

The L process looks like a classic synchronous request. What is the cleanest wholly asynchronous way to achieve this?

[wysota]

What is the cleanest wholly asynchronous way to achieve this?

I'd say a state machine plus a signal emission upon detection of a failed request due to session timeout. It's nothing difficult but I agree there are situations when doing things synchronously simplifies matters greatly.

[ChrisW67]

Good Morning Wysota,

Do you ever sleep?

I've just stocked up on caffeine to explore the state machine machine approach to something like the the scenario above with few extra quirks. I've not used QStateMachine in anger so this should be an interesting morning.

[wysota]

Good Morning Wysota,

Good morning

Do you ever sleep?

If I don't suffer from insomnia or don't have deadlines for the next day then in general - yes.

I've just stocked up on caffeine to explore the state machine machine approach to something like the the scenario above with few extra quirks. I've not used QStateMachine in anger so this should be an interesting morning.

By saying "state machine" I didn't exactly mean QStateMachine although of course it can be used here as well, it's just sometimes it's an overkill to use it when a simple enum variable holding the state would suffice