[Development] [API Change] New authentication method in QNetworkAccessManager
Kurt Pattyn
pattyn.kurt at gmail.com
Mon Mar 10 09:27:10 CET 2014
> On 10 Mar 2014, at 08:37, "Giuseppe D'Angelo" <dangelog at gmail.com> wrote:
>
>> On 10 March 2014 07:43, Kurt Pattyn <pattyn.kurt at gmail.com> wrote:
>> Is the documentation on the signal sslErrors() still correct then: "Note:
>> You cannot use Qt::QueuedConnection when connecting to this signal, or
>> calling QSslSocket::ignoreSslErrors() will have no effect." ?
>
> I presume it's still correct in order to retain compatibility with Qt
> 4. The new pausing mechanism is opt-in: you need to call
> setPauseMode(QAbstractSocket::PauseOnSslErrors) in order to make the
> socket pause when emitting sslErrors(). Once that signal gets emitted,
> the socket pauses and will not proceed further unless the user then
> calls ignoreSslErrors() + resume() or so.
But we can use a QueuedConnection if the PauseMode is set to PauseOnSslErrors, or can't we?
>
> To me this mechanism seems flexible enough to be coupled with anything...
>
> --
> Giuseppe D'Angelo
More information about the Development
mailing list