Trolltech Home | Qt-interest Home | Recent Threads | All Threads | Author | Date
All threads index page 4

Qt-interest Archive, January 2008
QSSL-Sockets with waitForReadyRead call / Qt 4.3

• Subject: QSSL-Sockets with waitForReadyRead call / Qt 4.3
• From: MWillmeroth@xxxxxxxxxxx
• Date: Thu, 31 Jan 2008 20:39:25 +0100
• Delivered-to: qt-interest@trolltech.com
• List-help: <mailto:qt-interest-request@trolltech.com?subject=help>
• List-post: <mailto:qt-interest@trolltech.com>
• List-subscribe: <mailto:qt-interest-request@trolltech.com?subject=subscribe>
• List-unsubscribe: <mailto:qt-interest-request@trolltech.com?subject=unsubscribe>
• Priority: normal
• Resent-from: qt-interest@xxxxxxxxxxxxx
• Resent-message-id: <G-3TGD.A.iSE.1QioHB@esparsett>
• Resent-sender: qt-interest-request@xxxxxxxxxxxxx
• To: qt-interest@xxxxxxxxxxxxx

Hello,

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?


Thanks in advance!

Winni




--
 [ signature omitted ]