Secure notification (TNtfnSClient) class

The TNtfnSClient class is derived from the abstract base class described in Abstract base notification class (TNtfnClientAPI). You use it to send secure-only and "secure-preferred" notifications.

The constructor for TNtfnSClient class does not establish a network connection with the UP.Link server; the API automatically connects each time it needs to--that is, when you call a method inherited from the TNtfnClientAPI base class to perform an operation such as posting, querying, or deleting a notification.

The TNtfnSClient class supports an optional "secure-preferred" mode, which attempts to use the non-secure notification port if the secure notification port is disabled. If you do not use the secure-preferred mode, calls to post, query, or delete notifications will fail if the API can't access the secure port.

Once the API successfully makes a request in secure-preferred mode, it binds the protocol used for the request to the TNtfnSClient object; it uses the protocol for subsequent requests. Specifically, if the API successfully makes a request to the secure port, it will not subsequently attempt to fail over to the non-secure port if the secure port becomes inaccessible. To determine which protocol the API is using, call the TNtfnClientAPI method, GetProtocol() (see GetProtocol()).

The TNtfnSClient class uses a secure protocol based on HTTPS.

The public interface of the TNtfnSClient class is defined as follows:

class TNtfnSClient: public TNtfnClientAPI
{
public:
    TNtfnSClient (const char *msgrHost,
        int requireSecure = 0,
        unsigned short upnotifypsPort = 0,
        unsigned short upnotifypPort = 0);

    int LoadCertAndKey (const char *filename,
        const char *passwd);
};

where:

You must call LoadCertAndKey() before you attempt to post, delete, or obtain status on a notification. LoadCertAndKey() returns nonzero for success, or zero if the specified file is not accessible or is malformed, or if the password you specify is incorrect.