Fast notifications interface

Basic information

As you might have read so far, wodSmtpCom can use fast notification interface instead of firing events. This means that each time wodSmtpCom needs to fire an event, it will call your implementation of the event instead. Notifications can be 30 times faster than events - meaning it is advised to be used if speed is needed in your applications.

wodSmtp ActiveX DOES NOT support notifications - only wodSmtpCom component does!

You must declare ALL notification methods if you want to implement IwodSmtpClientNotify, no matter if you need them or not. For example, many users don't need Connecting event, but at least empty body for this event MUST exist when notifications are used.

You can read below steps required to implement your own IwodSmtpClientNotify interface. As an example, we will put it on the main form. You can also put it into separate VB class, in which case instead of 'Me' keyword, you will use name of the class.

Steps needed to implement IwodSmtpClientNotify

1. Add Reference to wodSmtpCom COM Object to your application 2. Instead of declaring wodSmtp like this:

you should do this:

3. In Form_Load, create new instance for Smtp1, and pass reference of our IwodSmtpClientNotify to it

4. Implement ALL methods, or at least declare their empty bodies. You can do it automatically if you locate 'IwodSmtpClientNotify' object in the list of all objects existing on your form (combo box in upper left corner of your code view), or just can do it by hand.

5. All done. Now put breakpoints to your methods. You will see that instead of fired event, your methods will be called instead.

Method declarations

Platforms

Windows