Sure. SSL sockets are tcp Sockets, save for the negotiation. If you don't want
encryption, just don't call startServerEncription or the client version.
However, I would have to ask, why not just abstract it to be QTcpSocket*?
There is no overhead if you are encrypting.
In all my code, the only difference is if you are on a secure port, then you
start the encryption. Also, you should have some way of reporting the SSL
errors.
________________________________
From: Chaser <[email protected]>
To: [email protected]
Sent: Monday, November 21, 2011 12:06 PM
Subject: [Interest] Using QSslSocket as QTcpSocket
Hi all! Can a QSslSocket to work as QTcpSocket at unencrypted
connenctions? I don't want inherit from QTcpSocket for unencrypted
connenctions and from QSslSocket for encrypted connenctions, and have
two classes with duplicated code, so is it possible to use QSslSocket
for both cases?
And what about overhead and perfomance?
_______________________________________________
Interest mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/interest
