| Trolltech Home | Qt-interest Home | Recent Threads | All Threads | Author | Date | |
| All threads index page 1 | |
MWillmeroth@xxxxxxxxxxx wrote: >I have written a kind of client/server module which shall be used to >extend another Qt application for remote support. >Because everything works fine so far I have tried to add some security >by replacing QTcpSockets with QSslSockets. Now I found that a call to >QSslSocket::waitForReadyRead() blocks the main application even if >new data arrives at the socket. It seems to me that the readyRead >signal is never emitted until the waitForReadyRead call times out and >the event loop becomes active again. Why is that? Is the decryption of >the data done during the event loop? In this case a waitForReadyRead >call does not really make sense to me when using QSslSockets as one >has to go back to the main event loop anyway. > >Could anyone explain this to me? There were bugs in this code that I fixed for Qt 4.3.4 and 4.4.0. I am unsure now what exactly can be related to your problem, or if it has been fixed at all. In any case, can you test 4.4.0 snapshots and see if the problem is gone? If it's not, can you post a small, compileable example that shows the problem? -- [ signature omitted ]
Attachment:
signature.asc
Description: This is a digitally signed message part.