Back to product page
- Introduction
- Overview
- License Agrement
- Getting Started
- Objects
- Enumerations
- wodSSH
- Methods
- Properties
- AllocatePty
- Authentication
- Blocking
- ClientName
- Columns
- Command
- Compression
- DataOut
- DataReady
- Encoding
- Encryption
- EncryptionList
- ErrorText
- ExitSignal
- ExitStatus
- FIPS
- ForwardHost
- ForwardPort
- HMacList
- Hostname
- KeepAlives
- KeyExchangeList
- KeyForward
- KeySignatureList
- LastError
- Login
- MyHostname
- MyIP
- Notification
- Password
- Port
- PrivateKey
- Prompt
- Protocol
- ProxyHostname
- ProxyLogin
- ProxyPassword
- ProxyPort
- ProxyType
- RemoteIdentification
- Rows
- ShowStdErrorMessages
- State
- StateText
- StripANSI
- StripNull
- Subsystem
- TerminalSpeed
- TerminalType
- Timeout
- UseIPv6
- Version
- Events
- IwodSSHNotify
- How to get support?
- Technical information
- Fast notifications interface
- Error list
Blocking property
Determines if methods are blocking.
Type
A Boolean value. When set to True, methods are blocking.Syntax
- 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 wodSSH. |
value | A Boolean value. |
Remarks
Blocking mode is ideal for scripting environments when you cannot use asynchronous connections. Although events are still fired, you can just ignore them and check to see if an error occurred during method execution.The different behavior of blocking and non-blocking operations can be illustrated using the Connect method.
If Blocking is set to True, wodSSH will wait until it actually connects with the remote server before returning control. Once connected, control will be passed back to your program and you can continue with its execution. If an error is generated, control will be returned immediately.
If Blocking is set to False, wodSSH will immediately return after Connect is called, whether it managed to connect with the remote server (at that particular moment) or not. Following the call to Connect, you should wait for the Connected event to be fired to determine if Connect was successful or not.