> > > I also don't think you even need the 'no-openssl available' use case. > > > > While OpenSSL is commonly available on most systems. It may not be available > on all embedded platforms and it may not be the expected version. I can see > scenarios in which Websockets are needed, but OpenSSL is not available or not > desired by the user (e.g. embedded industrial apps that need to access some > networked resource with a very strange protocol[tm] while the boss insists > that > he would run into export restrictions if he allowed OpenSSL). > > > > > > Konrad > > If I may chime in, iOS officially doesn't provide OpenSSL and the > documentation > recommends to use Apple's own cryptographic framework. > > https://developer.apple.com/library/mac/DOCUMENTATION/Security/Concept > ual/cryptoservices/GeneralPurposeCrypto/GeneralPurposeCrypto.html >
Similar situation for Windows Phone. Maurice _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
