Back to product page
- Introduction
- License agreement
- Getting Started
- Enumerations
- Objects
- wodSmtp
- Methods
- Properties
- Authentication
- Blocking
- Certificate
- CharSet
- DNSHostname
- Hostname
- LastError
- LastErrorText
- Login
- MailFrom
- MailTo
- Message
- MyHostname
- MyIP
- Notification
- Password
- Port
- ProxyHostname
- ProxyLogin
- ProxyPassword
- ProxyPort
- ProxyType
- RequestReceipt
- RetryCount
- RetryWait
- Security
- State
- StateText
- Tag
- Timeout
- Transcript
- UseIPv6
- Version
- Events
- IwodSmtpClientNotify
- SmtpEncoder
- SmtpHdr
- SmtpHdrs
- SmtpMsg
- SmtpMsgs
- wodSmtp
- How to get support?
- Technical information
- Fast notifications interface
- Error list
Blocking Property
Determines if methods are blocking.
Type
BooleanSyntax
- Basic
object.Blocking [= value]
The Blocking(object,value) syntax has these parts:
The Blocking(object,value) syntax has these parts:
object | An expression evaluating to an object of type wodSmtp |
value | A Boolean value. |
Remarks
Blocking property determines if wodSmtp will block the thread where it executes, or it will work in async mode - in the background.When blocking is set, then when you issue, for example, SendMessage method, when it returns you will already have message delivered (if no error occurred). If any error occurs, it will be returned through SendMessage call - so you can catch it in your application. This is usable for scripting environments.
When blocking is not set, then when you issue, for example, SendMessage method, it will return the control to your program immediately, work in the background and download the message, and fire Done event when it finishes. If any error occurs, it will be provided in the Done event. From this event you can initiate new commands if needed.
When Blocking mode is used you should NOT initiate new commands from within wodSmtp's own events!