Nice work! I suppose you just want to replace the private implementation of QSSLSocket leaving the QSSLSocket header intact? QWebSockets depends further on the OpenSSL macro (can't remember the exact name now) to decide whether SSL sockets are supported. I think we also need another macro that indicates whether SSL is supported or not (and not just OpenSSL). If I can help, just let me know. I cannot test on an iOS device though.
Cheers, Kurt >> On 29 Apr 2014, at 18:36, Jeremy Lainé <jeremy.la...@m4x.org> wrote: >> >> On 04/29/2014 02:39 PM, Sorvig Morten wrote: >> This aproach looks promising. If we can get basic QSslSocket working (enough >> for say QNAM and QWebSocket) then retiring the NSUrlConnection backend and >> focusing on QSslSocket is a possibility. > > OK I have moved my proof of concept code here: > > https://github.com/jlaine/qsslsocketios > > I provided a demo app : a very naive HTTPS client which fetches > https://www.google.com and dumps it to standard out. > > You can run this on any OSX machine with Qt installed. > > I'll start looking how hard it would be to actually integrate this into > qtbase. > > Cheers, > Jeremy > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
