Re: [Development] [API Change] New authentication method in QNetworkAccessManager

2014-03-10 Thread Giuseppe D'Angelo
On 10 March 2014 09:27, Kurt Pattyn wrote: > But we can use a QueuedConnection if the PauseMode is set to > PauseOnSslErrors, or can't we? The idea is that you can. The socket will be paused and won't proceed until a call to resume. If the QueuedConnection usage comes from the idea of using mul

Re: [Development] [API Change] New authentication method in QNetworkAccessManager

2014-03-10 Thread Kurt Pattyn
> On 10 Mar 2014, at 08:37, "Giuseppe D'Angelo" wrote: > >> On 10 March 2014 07:43, Kurt Pattyn 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()

Re: [Development] [API Change] New authentication method in QNetworkAccessManager

2014-03-10 Thread Giuseppe D'Angelo
On 10 March 2014 07:43, Kurt Pattyn 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

Re: [Development] [API Change] New authentication method in QNetworkAccessManager

2014-03-09 Thread Kurt Pattyn
> On 09 Mar 2014, at 22:46, Richard Moore wrote: > >> > >> > IIRC SSL sockets had the same "issue" when SSL errors are raised. Has >> > it been solved there? How? >> AFAIK, it has not been solved. The problem is the same. > > It has been partially solved, in recent versions you can set the soc

Re: [Development] [API Change] New authentication method in QNetworkAccessManager

2014-03-09 Thread Richard Moore
On 9 March 2014 20:13, Kurt Pattyn wrote: > > On 09 Mar 2014, at 21:02, Giuseppe D'Angelo wrote: > > > On 9 March 2014 15:10, Kurt Pattyn wrote: > >> Also, the connection between the authenticationRequired signal and the > slot > >> must be a direct connection. > > > > IIRC SSL sockets had the

Re: [Development] [API Change] New authentication method in QNetworkAccessManager

2014-03-09 Thread Kurt Pattyn
On 09 Mar 2014, at 21:02, Giuseppe D'Angelo wrote: > On 9 March 2014 15:10, Kurt Pattyn wrote: >> Also, the connection between the authenticationRequired signal and the slot >> must be a direct connection. > > IIRC SSL sockets had the same "issue" when SSL errors are raised. Has > it been solv

Re: [Development] [API Change] New authentication method in QNetworkAccessManager

2014-03-09 Thread Kurt Pattyn
On 09 Mar 2014, at 19:32, Olivier Goffart wrote: > On Sunday 09 March 2014 15:10:02 Kurt Pattyn wrote: >> Currently, QNAM stalls when authentication is required (also see: >> https://bugreports.qt-project.org/browse/QTBUG-16251). Also, the connection >> between the authenticationRequired signal

Re: [Development] [API Change] New authentication method in QNetworkAccessManager

2014-03-09 Thread Giuseppe D'Angelo
On 9 March 2014 15:10, Kurt Pattyn wrote: > Also, the connection between the authenticationRequired signal and the slot > must be a direct connection. IIRC SSL sockets had the same "issue" when SSL errors are raised. Has it been solved there? How? -- Giuseppe D'Angelo __

Re: [Development] [API Change] New authentication method in QNetworkAccessManager

2014-03-09 Thread Olivier Goffart
On Sunday 09 March 2014 15:10:02 Kurt Pattyn wrote: > Currently, QNAM stalls when authentication is required (also see: > https://bugreports.qt-project.org/browse/QTBUG-16251). Also, the connection > between the authenticationRequired signal and the slot must be a direct > connection. This is probl

Re: [Development] [API Change] New authentication method in QNetworkAccessManager

2014-03-09 Thread Kurt Pattyn
On 09 Mar 2014, at 17:50, Kevin Krammer wrote: > On Sunday, 2014-03-09, 15:10:02, Kurt Pattyn wrote: >> Currently, QNAM stalls when authentication is required (also see: >> https://bugreports.qt-project.org/browse/QTBUG-16251). Also, the connection >> between the authenticationRequired signal an

Re: [Development] [API Change] New authentication method in QNetworkAccessManager

2014-03-09 Thread Kurt Pattyn
On 09 Mar 2014, at 17:16, Konstantin Ritt wrote: > > 2014-03-09 16:10 GMT+02:00 Kurt Pattyn : > Currently, QNAM stalls when authentication is required (also see: > https://bugreports.qt-project.org/browse/QTBUG-16251). > Also, the connection between the authenticationRequired signal and the sl

Re: [Development] [API Change] New authentication method in QNetworkAccessManager

2014-03-09 Thread Kevin Krammer
On Sunday, 2014-03-09, 15:10:02, Kurt Pattyn wrote: > Currently, QNAM stalls when authentication is required (also see: > https://bugreports.qt-project.org/browse/QTBUG-16251). Also, the connection > between the authenticationRequired signal and the slot must be a direct > connection. This is probl

Re: [Development] [API Change] New authentication method in QNetworkAccessManager

2014-03-09 Thread Konstantin Ritt
2014-03-09 16:10 GMT+02:00 Kurt Pattyn : > Currently, QNAM stalls when authentication is required (also see: > https://bugreports.qt-project.org/browse/QTBUG-16251). > Also, the connection between the authenticationRequired signal and the > slot must be a direct connection. > This is problematic w

[Development] [API Change] New authentication method in QNetworkAccessManager

2014-03-09 Thread Kurt Pattyn
Currently, QNAM stalls when authentication is required (also see: https://bugreports.qt-project.org/browse/QTBUG-16251). Also, the connection between the authenticationRequired signal and the slot must be a direct connection. This is problematic when an application wants to show a login dialogbox