wxWindows class (not implemented over SSL) name |
corresponding wxSSL class (implemented over SSL) name |
| wxTCPConnection | wxSSLConnection |
| wxTCPClient | wxSSLClient |
| wxTCPServer | wxSSLServer |
| wxSocketBase | wxSSLSocketBase |
| wxSocketClient | wxSSLSocketClient |
| wxSocketServer | wxSSLSocketServer |
| wxProtocol | wxSSLProtocol |
| wxHTTP | wxHTTPS |
| wxFTP | wxSFTP |
Please ensure that any C/C++ code written follows the wxWindows Coding Guidelines.
If you write optimized assembler procedures for a particular processor architecture, a fallback written in C/C++ must be implemented and the fallback should follow the wxSSL Implementation Guidelines.
Make code compatible with all wxWindows platforms that support wxWindows socket classes.
Copy and paste code from the non-SSL versions of the classes to the SSL versions of the classes instead of deriving from the corresponding non-SSL class (Exceptions: derive wxSSLClient from wxClientBase, derive wxSSLServer from wxServerBase, derive wxSSLConnection from wxConnectionBase).
Derive wxHTTPS and wxSFTP from wxSSLProtocol.
Use wxWindows socket classes to write SSL protocol support wherever possible.
Make all classes fully compliant with the SSL 2.0 standard, the SSL 3.0 standard, and the TLS 1.0 standard.