Initializing the Secure Sockets Package
Your application must initialize the cryptographic library before calling it and must terminate it immediately after the last cryptographic call. The initialization and termination functions allocate and free resources used by the cryptographic library.
RWSecureSocketPackageInit encapsulates these initialization and termination functions in its constructor and destructor.
NOTE: Because the instance of RWSecureSocketPackageInit must be active during all calls to the Secure Sockets package, we recommend that you create a global instance of RWSecureSocketPackageInit. Also, refrain from using Secure Sockets package functions in the constructors of other global objects.
If you do not have any global objects that require the Secure Sockets package during their construction, you can instantiate
RWSecureSocketPackageInit in your
main() function. See the examples in
Getting Started with Secure Sockets. 
