I’d like to second (third?) going for approach 1.
It’s possible that we would want to implement secure socket support for
QWebSocket using native API instead of QTcpSocket
and OpenSSL at some point. We are currently doing this for
QNetworkAccessManager on OS X and iOS
Using QSslConfiguration exclusively is a good idea, and removes most of the
QSslSocket functions.
Also consider which functions / signals are handled internal to websocket.
e.g. encrypted, encryptedBytesWritten may be internal since websocket is
message based.
If the handling of the signal is
Hi,
I would like to add secure sockets support to the QWebSocket class (see
QtWebSockets add-on at https://qt.gitorious.org/qtplayground/websockets).
Currently, a connection is made to a web socket server, as follows:
QWebSocket webSocket;
webSocket.open(QUrl(“ws://someserver”));
On domingo, 27 de outubro de 2013 11:07:39, Kurt Pattyn wrote:
Hi,
I would like to add secure sockets support to the QWebSocket class (see
QtWebSockets add-on at https://qt.gitorious.org/qtplayground/websockets).
Currently, a connection is made to a web socket server, as follows:
QWebSocket
