[Interest] Is freshly created QNetworkReply guaranteed to be in non-finished state and emit finished signal?

[ekke]

Am 19.04.17 um 22:58 schrieb Thiago Macieira:
> On quarta-feira, 19 de abril de 2017 13:15:23 PDT Reinhardt Behm wrote:
>> On Wednesday 19 April 2017 11:03:48 Thiago Macieira wrote:
>>> It's guaranteed not to be finished.
>> Doesn't QAN use it's own thread? 
> Irrelevant.
>
>> Then it could already be finished before the connection is made.
> It can't happen. This is a design guarantee and will continue to work however 
> much we change QNAM.
>
> That said, for certain URLs (namely, "file:///"), isFinished() may return true, 
> in which case you can obtain the data immediately. But even if that is the 
> case, finished() will still be emitted.
>
what happens on mobile platforms if APP is suspended, then coming back
to active
will finished() always be received ?

haven't tested this in detail yet for QNAM requests

I already tested QNetworkConfigurationManager on Android, where signals
(onlineStateChanged) are queued while suspended
coming back to active all signals are received.
tested this with App 10 minutes suspended and switching airplane mode
on- off

ekke