XMPP Component
Properties Methods Events Config Settings Errors
The XMPP Component is used to create a lightweight messaging client using the XMPP (Jabber) protocol.
Syntax
TiotXMPP
Remarks
The XMPP component supports both plaintext and SSL/TLS connections. When connecting over SSL/TLS the SSLServerAuthentication event allows you to check the server identity and other security attributes. The SSLStatus event provides information about the SSL handshake. Additional SSL related settings are also supported via the Config method.
A call to the ConnectTo method will perform the entire logon process after which a Connected event will fire indicating connection status. For simplicity, the entire interface is synchronous; the component will not return until a call is completed.
After a successful connection, the component will automatically begin the process of receiving the user's buddy list. The component will parse the XML as it comes in from the server and will set the appropriate properties. Once the entire buddy list has been retrieved, a Sync event will fire.
Sending a message is as simple as calling a single method. One call to the SendMessage method will cause the component to connect if it has not already done so, send the specified message to a specified user, and return to the original connection state.
The XMPP Component interface supports messaging, list and presence management. Other features of the XMPP protocol are supported through the SendCommand method and PITrail event.
Example (Connecting and Sending a Message)
IMControl.ConnectTo("myusername", "mypassword")
IMControl.MessageText = "My Message"
IMControl.SendMessage("ToUser")
Example (Sending a Single Message)
IMControl.User = "myusername"
IMControl.Password = "mypassword"
IMControl.MessageText = "My Message"
IMControl.SendMessage("ToUser")
Property List
The following is the full list of the properties of the component with short descriptions. Click on the links for further details.
AuthDomain | The domain under which the user will be authenticated. |
AuthMethods | Controls how the component authenticates itself with the XMPP server. |
BuddyCount | The number of records in the Buddy arrays. |
BuddyGroup | This is a comma-separated list of the buddy's associated groups. |
BuddyId | This is the jabber id of the buddy. |
BuddyNickName | The nickname of the buddy, if one exists. |
BuddyRealName | The real name of the buddy. |
BuddySubscription | This is a list of the subscription status for the buddy. |
Connected | This indicates the component's login status. |
FirewallAutoDetect | This property tells the component whether or not to automatically detect and use firewall system settings, if available. |
FirewallType | This property determines the type of firewall to connect through. |
FirewallHost | This property contains the name or IP address of firewall (optional). |
FirewallPassword | This property contains a password if authentication is to be used when connecting through the firewall. |
FirewallPort | This property contains the transmission control protocol (TCP) port for the firewall Host . |
FirewallUser | This property contains a user name if authentication is to be used connecting through a firewall. |
IMPort | The server port for XMPP (default 5222). |
IMServer | This is the instant messaging server. |
LocalDirectory | The directory to which received files are saved. |
LocalFile | The path to the file that will be sent. |
LocalHost | The name of the local host or user-assigned IP interface through which connections are initiated or accepted. |
MessageHTML | This is the HTML version of the current message. |
MessageOtherData | This property contains extra data elements for the current message. |
MessageSubject | This is the subject of the current message. |
MessageText | This is the plain text of the current message. |
MessageThread | This is the thread name of the current message. |
MessageType | This is the type of the current message. |
Password | This is the user's password. |
Presence | This is the availability of the entity. |
Resource | This is the resource for the current session. |
ServerDomain | The XMPP server's domain. |
SSLAcceptServerCertEncoded | This is the certificate (PEM/base64 encoded). |
SSLCertEncoded | This is the certificate (PEM/base64 encoded). |
SSLCertStore | This is the name of the certificate store for the client certificate. |
SSLCertStorePassword | If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store. |
SSLCertStoreType | This is the type of certificate store for this certificate. |
SSLCertSubject | This is the subject of the certificate used for client authentication. |
SSLEnabled | Whether TLS/SSL is enabled. |
SSLProvider | This specifies the SSL/TLS implementation to use. |
SSLServerCertEncoded | This is the certificate (PEM/base64 encoded). |
SSLStartMode | Determines how the component starts the SSL negotiation. |
Status | Description of the availability of this entity. |
Timeout | A timeout for the component. |
User | The user portion of this entity's Jabber ID. |
UserDomain | Gets or sets the domain value used for Jabber IDs. |
UserInfoCount | The number of records in the UserInfo arrays. |
UserInfoField | This is the name of the current property necessary for registration. |
UserInfoValue | This is the value for the current registration property, and should be set after calling QueryRegister and before calling Register . |
Method List
The following is the full list of the methods of the component with short descriptions. Click on the links for further details.
Add | This method will add an entity to this entity's roster. |
Cancel | This will cancel another entity's subscription to this entity's presence. |
ChangePassword | This method will change the current user's password. |
ChangePresence | This method will set the availability and status of this entity. |
Config | Sets or retrieves a configuration setting. |
Connect | This method will connect the component to the server. |
ConnectTo | This method will connect the component to the server. |
Disconnect | This method disconnects the component from the server. |
DoEvents | This method processes events from the internal message queue. |
Interrupt | Interrupt the current method. |
ProbePresence | Use this method to probe for another entity's presence. |
QueryRegister | This method queries a server for the necessary registration fields. |
Register | This method registers an account with a server. |
Remove | This method will remove an entity from this entity's roster. |
Reset | Reset the component. |
RetrieveRoster | This method will retrieve this entity's roster from the server. |
SendCommand | This method sends a command to the server. |
SendFile | Sends a file to the specified user. |
SendMsg | This method will send a message to the specified user. |
SetUserInfoField | This method will add a user information field for registration. |
SubscribeTo | Use this method to subscribe to another entity's presence. |
Unregister | This method cancels an account with the host. |
UnsubscribeTo | This method will cancel a subscription to another entity's presence. |
UpdateBuddyGroup | Updates the buddy's associatd groups. |
Event List
The following is the full list of the events fired by the component with short descriptions. Click on the links for further details.
BuddyUpdate | This event is fired whenever a roster entry is updated. |
Connected | This event is fired when a connection to the IM Server is completed. |
ConnectionStatus | This event is fired to indicate changes in the connection state. |
Disconnected | This event is fired when the chat service connection is lost. |
EndTransfer | Fired when a file transfer completes. |
Error | This event is fired when the server sends a protocol error message. |
IQ | This event is fired for IQ messages not normally supported by the component. |
MessageIn | This event is fired upon receipt of a message. |
PITrail | This event is fired for all protocol messages. |
Presence | This event is fired when the presence of a subscribed entity changes. |
ReadyToSend | This event is fired when the component is ready to send data. |
SSLServerAuthentication | Fired after the server presents its certificate to the client. |
SSLStatus | Shows the progress of the secure connection. |
StartTransfer | Fired when a file transfer begins. |
SubscriptionRequest | This event fires when a subscription request is received. |
Sync | This event fires upon a complete information synchronization with the server. |
Transfer | Fired during file transfer. |
Config Settings
The following is a list of config settings for the component with short descriptions. Click on the links for further details.
AccessToken | The OAuth access token used for authentication. |
BlockSize | Specifies the block size for file transfers. |
ClientId | The OAuth client Id used for authentication. |
MessageXML | Returns the last root-level element received by the component. |
Overwrite | Specifies whether or not to overwrite received files. |
ParseHTML | Tells XMPP whether or not to parse MessageHTML when it's set. |
RetrieveRoster | Whether to automatically retrieve the roster when logging in. |
SendSubscriptionResponse | Determines whether a response will be sent to a Subscription Request. |
UseCompression | Specified whether or not stream compression is used. |
ConnectionTimeout | Sets a separate timeout value for establishing a connection. |
FirewallAutoDetect | Tells the component whether or not to automatically detect and use firewall system settings, if available. |
FirewallHost | Name or IP address of firewall (optional). |
FirewallPassword | Password to be used if authentication is to be used when connecting through the firewall. |
FirewallPort | The TCP port for the FirewallHost;. |
FirewallType | Determines the type of firewall to connect through. |
FirewallUser | A user name if authentication is to be used connecting through a firewall. |
KeepAliveInterval | The retry interval, in milliseconds, to be used when a TCP keep-alive packet is sent and no response is received. |
KeepAliveTime | The inactivity time in milliseconds before a TCP keep-alive packet is sent. |
Linger | When set to True, connections are terminated gracefully. |
LingerTime | Time in seconds to have the connection linger. |
LocalHost | The name of the local host through which connections are initiated or accepted. |
LocalPort | The port in the local host where the component binds. |
MaxLineLength | The maximum amount of data to accumulate when no EOL is found. |
MaxTransferRate | The transfer rate limit in bytes per second. |
ProxyExceptionsList | A semicolon separated list of hosts and IPs to bypass when using a proxy. |
TCPKeepAlive | Determines whether or not the keep alive socket option is enabled. |
TcpNoDelay | Whether or not to delay when sending packets. |
UseIPv6 | Whether to use IPv6. |
LogSSLPackets | Controls whether SSL packets are logged when using the internal security API. |
OpenSSLCADir | The path to a directory containing CA certificates. |
OpenSSLCAFile | Name of the file containing the list of CA's trusted by your application. |
OpenSSLCipherList | A string that controls the ciphers to be used by SSL. |
OpenSSLPrngSeedData | The data to seed the pseudo random number generator (PRNG). |
ReuseSSLSession | Determines if the SSL session is reused. |
SSLCACerts | A newline separated list of CA certificate to use during SSL client authentication. |
SSLCheckCRL | Whether to check the Certificate Revocation List for the server certificate. |
SSLCheckOCSP | Whether to use OCSP to check the status of the server certificate. |
SSLCipherStrength | The minimum cipher strength used for bulk encryption. |
SSLEnabledCipherSuites | The cipher suite to be used in an SSL negotiation. |
SSLEnabledProtocols | Used to enable/disable the supported security protocols. |
SSLEnableRenegotiation | Whether the renegotiation_info SSL extension is supported. |
SSLIncludeCertChain | Whether the entire certificate chain is included in the SSLServerAuthentication event. |
SSLKeyLogFile | The location of a file where per-session secrets are written for debugging purposes. |
SSLNegotiatedCipher | Returns the negotiated cipher suite. |
SSLNegotiatedCipherStrength | Returns the negotiated cipher suite strength. |
SSLNegotiatedCipherSuite | Returns the negotiated cipher suite. |
SSLNegotiatedKeyExchange | Returns the negotiated key exchange algorithm. |
SSLNegotiatedKeyExchangeStrength | Returns the negotiated key exchange algorithm strength. |
SSLNegotiatedVersion | Returns the negotiated protocol version. |
SSLSecurityFlags | Flags that control certificate verification. |
SSLServerCACerts | A newline separated list of CA certificate to use during SSL server certificate validation. |
TLS12SignatureAlgorithms | Defines the allowed TLS 1.2 signature algorithms when SSLProvider is set to Internal. |
TLS12SupportedGroups | The supported groups for ECC. |
TLS13KeyShareGroups | The groups for which to pregenerate key shares. |
TLS13SignatureAlgorithms | The allowed certificate signature algorithms. |
TLS13SupportedGroups | The supported groups for (EC)DHE key exchange. |
AbsoluteTimeout | Determines whether timeouts are inactivity timeouts or absolute timeouts. |
FirewallData | Used to send extra data to the firewall. |
InBufferSize | The size in bytes of the incoming queue of the socket. |
OutBufferSize | The size in bytes of the outgoing queue of the socket. |
BuildInfo | Information about the product's build. |
CodePage | The system code page used for Unicode to Multibyte translations. |
LicenseInfo | Information about the current license. |
MaskSensitive | Whether sensitive data is masked in log messages. |
UseInternalSecurityAPI | Tells the component whether or not to use the system security libraries or an internal implementation. |
AuthDomain Property (XMPP Component)
The domain under which the user will be authenticated.
Syntax
__property String AuthDomain = { read=FAuthDomain, write=FSetAuthDomain };
Default Value
""
Remarks
Set this value if the user must authenticate via a third party authentication service that requires a different domain than the XMPP user's registered domain.
Data Type
String
AuthMethods Property (XMPP Component)
Controls how the component authenticates itself with the XMPP server.
Syntax
__property String AuthMethods = { read=FAuthMethods, write=FSetAuthMethods };
Default Value
"*"
Remarks
AuthMethods is a comma-separated list of authentication methods to be enabled on the component, listed in order of preference. When authenticating, the component will pick the first method in the list that is supported by the server.
The special value * (default) may be supplied to cause the component to enable all supported authentication methods in order of presumed security. The XMPP component currently supports the following values for AuthMethods, listed in order of most secure to least secure:
- SASL/DIGEST-MD5
- AuthIQ/Digest
- SASL/CRAM-MD5
- SASL/PLAIN
- AuthIQ/Plaintext
- SASL/NTLM
Data Type
String
BuddyCount Property (XMPP Component)
The number of records in the Buddy arrays.
Syntax
__property int BuddyCount = { read=FBuddyCount };
Default Value
0
Remarks
This property controls the size of the following arrays:
The array indices start at 0 and end at BuddyCount - 1.This property is read-only and not available at design time.
Data Type
Integer
BuddyGroup Property (XMPP Component)
This is a comma-separated list of the buddy's associated groups.
Syntax
__property String BuddyGroup[int BuddyIndex] = { read=FBuddyGroup, write=FSetBuddyGroup };
Default Value
""
Remarks
This is a comma-separated list of the buddy's associated groups.
After the Sync event has fired, this property will contain a comma-separated list of groups for the associated BuddyId. Changing this value will cause the buddy's group associations to change. Setting it to the empty string ("") will cause the buddy to be completely disassociated from all groups.
Note: It is recommended to use the UpdateBuddyGroup method instead of setting this property.
The BuddyIndex parameter specifies the index of the item in the array. The size of the array is controlled by the BuddyCount property.
This property is not available at design time.
Data Type
String
BuddyId Property (XMPP Component)
This is the jabber id of the buddy.
Syntax
__property String BuddyId[int BuddyIndex] = { read=FBuddyId };
Default Value
""
Remarks
This is the jabber id of the buddy.
After a Sync event is fired, this property will contain the user id associated with the corresponding entry in the buddy list. If a buddy has multiple entries (e.g., if the buddy is listed in several groups) more than one entry will be the same.
The BuddyIndex parameter specifies the index of the item in the array. The size of the array is controlled by the BuddyCount property.
This property is read-only and not available at design time.
Data Type
String
BuddyNickName Property (XMPP Component)
The nickname of the buddy, if one exists.
Syntax
__property String BuddyNickName[int BuddyIndex] = { read=FBuddyNickName, write=FSetBuddyNickName };
Default Value
""
Remarks
The nickname of the buddy, if one exists.
The BuddyIndex parameter specifies the index of the item in the array. The size of the array is controlled by the BuddyCount property.
This property is not available at design time.
Data Type
String
BuddyRealName Property (XMPP Component)
The real name of the buddy.
Syntax
__property String BuddyRealName[int BuddyIndex] = { read=FBuddyRealName };
Default Value
""
Remarks
The real name of the buddy.
The BuddyIndex parameter specifies the index of the item in the array. The size of the array is controlled by the BuddyCount property.
This property is read-only and not available at design time.
Data Type
String
BuddySubscription Property (XMPP Component)
This is a list of the subscription status for the buddy.
Syntax
__property TiotXMPPBuddySubscriptions BuddySubscription[int BuddyIndex] = { read=FBuddySubscription };
enum TiotXMPPBuddySubscriptions { stNone=0, stTo=1, stFrom=2, stBoth=3, stRemove=4 };
Default Value
stNone
Remarks
This is a list of the subscription status for the buddy.
After a Sync event is fired, this property will contain all of the types of subscriptions for the buddy. They are defined as follows:
stNone (0) | no subscription |
stTo (1) | the buddy has a subscription to this entity. |
stFrom (2) | this entity has a subscription to the buddy |
stBoth (3) | subscription is both to and from |
stRemove (4) | the item is to be removed from the list |
The BuddyIndex parameter specifies the index of the item in the array. The size of the array is controlled by the BuddyCount property.
This property is read-only and not available at design time.
Data Type
Integer
Connected Property (XMPP Component)
This indicates the component's login status.
Syntax
__property bool Connected = { read=FConnected, write=FSetConnected };
Default Value
False
Remarks
This value shows whether or not the component has successfully logged into the IMServer. It will not be true until a successful Connected event has fired.
Note: It is recommended to use the Connect or Disconnect method instead of setting this property.
This property is not available at design time.
Data Type
Boolean
FirewallAutoDetect Property (XMPP Component)
This property tells the component whether or not to automatically detect and use firewall system settings, if available.
Syntax
__property bool FirewallAutoDetect = { read=FFirewallAutoDetect, write=FSetFirewallAutoDetect };
Default Value
False
Remarks
This property tells the component whether or not to automatically detect and use firewall system settings, if available.
Data Type
Boolean
FirewallType Property (XMPP Component)
This property determines the type of firewall to connect through.
Syntax
__property TiotXMPPFirewallTypes FirewallType = { read=FFirewallType, write=FSetFirewallType };
enum TiotXMPPFirewallTypes { fwNone=0, fwTunnel=1, fwSOCKS4=2, fwSOCKS5=3, fwSOCKS4A=10 };
Default Value
fwNone
Remarks
This property determines the type of firewall to connect through. The applicable values are as follows:
fwNone (0) | No firewall (default setting). |
fwTunnel (1) | Connect through a tunneling proxy. FirewallPort is set to 80. |
fwSOCKS4 (2) | Connect through a SOCKS4 Proxy. FirewallPort is set to 1080. |
fwSOCKS5 (3) | Connect through a SOCKS5 Proxy. FirewallPort is set to 1080. |
fwSOCKS4A (10) | Connect through a SOCKS4A Proxy. FirewallPort is set to 1080. |
Data Type
Integer
FirewallHost Property (XMPP Component)
This property contains the name or IP address of firewall (optional).
Syntax
__property String FirewallHost = { read=FFirewallHost, write=FSetFirewallHost };
Default Value
""
Remarks
This property contains the name or IP address of firewall (optional). If a FirewallHost is given, the requested connections will be authenticated through the specified firewall when connecting.
If this property is set to a Domain Name, a DNS request is initiated. Upon successful termination of the request, this property is set to the corresponding address. If the search is not successful, the component raises an exception.
Data Type
String
FirewallPassword Property (XMPP Component)
This property contains a password if authentication is to be used when connecting through the firewall.
Syntax
__property String FirewallPassword = { read=FFirewallPassword, write=FSetFirewallPassword };
Default Value
""
Remarks
This property contains a password if authentication is to be used when connecting through the firewall. If FirewallHost is specified, the FirewallUser and FirewallPassword properties are used to connect and authenticate to the given firewall. If the authentication fails, the component raises an exception.
Data Type
String
FirewallPort Property (XMPP Component)
This property contains the transmission control protocol (TCP) port for the firewall Host .
Syntax
__property int FirewallPort = { read=FFirewallPort, write=FSetFirewallPort };
Default Value
0
Remarks
This property contains the transmission control protocol (TCP) port for the firewall FirewallHost. See the description of the FirewallHost property for details.
Note: This property is set automatically when FirewallType is set to a valid value. See the description of the FirewallType property for details.
Data Type
Integer
FirewallUser Property (XMPP Component)
This property contains a user name if authentication is to be used connecting through a firewall.
Syntax
__property String FirewallUser = { read=FFirewallUser, write=FSetFirewallUser };
Default Value
""
Remarks
This property contains a user name if authentication is to be used connecting through a firewall. If the FirewallHost is specified, this property and FirewallPassword properties are used to connect and authenticate to the given Firewall. If the authentication fails, the component raises an exception.
Data Type
String
IMPort Property (XMPP Component)
The server port for XMPP (default 5222).
Syntax
__property int IMPort = { read=FIMPort, write=FSetIMPort };
Default Value
5222
Remarks
For implicit SSL, use port 5223 (please refer to the SSLStartMode property for more information).
A valid port number (a value between 1 and 65535) is required for the connection to take place. The property must be set before a connection is attempted and cannot be changed once a connection is established. Any attempt to change this property while connected will fail with an error.
Data Type
Integer
IMServer Property (XMPP Component)
This is the instant messaging server.
Syntax
__property String IMServer = { read=FIMServer, write=FSetIMServer };
Default Value
""
Remarks
This is the instant messaging server to which the component will connect when the Connect method is called. The IMServer property must contain a valid XMPP (Jabber) server, or any subsequent calls to the Connect method will fail.
Data Type
String
LocalDirectory Property (XMPP Component)
The directory to which received files are saved.
Syntax
__property String LocalDirectory = { read=FLocalDirectory, write=FSetLocalDirectory };
Default Value
""
Remarks
This setting specifies the directory on disk to which received files will be saved. If this property is not set and a file is received the file data will be available through the Transfer event parameters. This property may also be set when the StartTransfer event fires.
Data Type
String
LocalFile Property (XMPP Component)
The path to the file that will be sent.
Syntax
__property String LocalFile = { read=FLocalFile, write=FSetLocalFile };
Default Value
""
Remarks
This property specifies the local file that will be sent when calling SendFile. This property must be set before calling SendFile.
Data Type
String
LocalHost Property (XMPP Component)
The name of the local host or user-assigned IP interface through which connections are initiated or accepted.
Syntax
__property String LocalHost = { read=FLocalHost, write=FSetLocalHost };
Default Value
""
Remarks
The LocalHost property contains the name of the local host as obtained by the gethostname() system call, or if the user has assigned an IP address, the value of that address.
In multi-homed hosts (machines with more than one IP interface) setting LocalHost to the value of an interface will make the component initiate connections (or accept in the case of server components) only through that interface.
If the component is connected, the LocalHost property shows the IP address of the interface through which the connection is made in internet dotted format (aaa.bbb.ccc.ddd). In most cases, this is the address of the local host, except for multi-homed hosts (machines with more than one IP interface).
NOTE: LocalHost is not persistent. You must always set it in code, and never in the property window.
Data Type
String
MessageHTML Property (XMPP Component)
This is the HTML version of the current message.
Syntax
__property String MessageHTML = { read=FMessageHTML, write=FSetMessageHTML };
Default Value
""
Remarks
If the user wishes to send any HTML as a part of the message, it must be set in the MessageHTML property. The HTML must be an entire HTML document, including the <html> and <body> tags. If the HTML has unbalanced tags, the XMPP component will fail with an error.
This property is not available at design time.
Data Type
String
MessageOtherData Property (XMPP Component)
This property contains extra data elements for the current message.
Syntax
__property String MessageOtherData = { read=FMessageOtherData, write=FSetMessageOtherData };
Default Value
""
Remarks
MessageOtherData will contain zero or more complete XML elements associated with the message, but which are not defined in the Jabber specification.
Data Type
String
MessageSubject Property (XMPP Component)
This is the subject of the current message.
Syntax
__property String MessageSubject = { read=FMessageSubject, write=FSetMessageSubject };
Default Value
""
Remarks
MessageSubject will contain any subject associated with the message. Most Jabber clients will ignore the subject unless the message is of type "headline".
This property is not available at design time.
Data Type
String
MessageText Property (XMPP Component)
This is the plain text of the current message.
Syntax
__property String MessageText = { read=FMessageText, write=FSetMessageText };
Default Value
""
Remarks
MessageText is the plain text version of the current message, taken from the message's "body" child element. The text in this property is automatically escaped to ensure valid XML parsing on the other end.
This property is not available at design time.
Data Type
String
MessageThread Property (XMPP Component)
This is the thread name of the current message.
Syntax
__property String MessageThread = { read=FMessageThread, write=FSetMessageThread };
Default Value
""
Remarks
MessageThread will contain the name of the thread associated with the message. Threads are useful for tracking messages of type "chat" or "groupchat".
This property is not available at design time.
Data Type
String
MessageType Property (XMPP Component)
This is the type of the current message.
Syntax
__property TiotXMPPMessageTypes MessageType = { read=FMessageType, write=FSetMessageType };
enum TiotXMPPMessageTypes { jmtNormal=0, jmtChat=1, jmtGroupChat=2, jmtHeadline=3, jmtError=4 };
Default Value
jmtNormal
Remarks
MessageType is the type of the message as specified in the XMPP RFC. The possible values are defined in the protocol specification as follows:
normal (jmtNormal - 0) | A single message. |
chat (jmtChat - 1) | A message sent in the context of two-way chat between two entities. |
groupchat (jmtGroupChat - 2) | A message sent in the context of multi-user chat among multiple entities. |
headline (jmtHeadline - 3) | A message that represents one of a list of items (e.g., in a news feed or information ticker). |
error (jmtError - 4) | A message returned to a sender specifying an error associated with a previous message sent by the sender to an intended recipient. |
This property is not available at design time.
Data Type
Integer
Password Property (XMPP Component)
This is the user's password.
Syntax
__property String Password = { read=FPassword, write=FSetPassword };
Default Value
""
Remarks
This must be set before a connection is attempted. If a call to the Connect method is made specifying a password, the Password property will contain that password.
Data Type
String
Presence Property (XMPP Component)
This is the availability of the entity.
Syntax
__property TiotXMPPPresences Presence = { read=FPresence, write=FSetPresence };
enum TiotXMPPPresences { pcOffline=0, pcChat=1, pcAway=2, pcXA=3, pcDND=4 };
Default Value
pcChat
Remarks
When the component completes the initial log in, it will send information telling other entities subscribed to this entity's presence that it is online. The application must provide different status and availability information as the user changes them.
The Presence property has one of four values representing general information about the user's status as defined in the Jabber protocol specification:
pcOffline (0) | Invisible: JabberId is offline. |
pcChat (1) | Available: JabberId is online. |
pcAway (2) | Away: JabberId is online, but the user is away from their computer. |
pcXA (3) | Extended Away: JabberId is online, but the user is away from their computer for an extended period of time. |
pcDND (4) | Do not Disturb: JabberId is online, but is busy and does not wish to be disturbed. |
By default, the component sets the client presence to pcChat, meaning that the user is available. To change the initial status sent by the component set Presence to the desired presence before calling Connect.
Note: offline is not officially supported by the XMPP specification, however some XMPP server implementations may recognize the value. Setting the client's presence state to this value may cause the server to respond with an Error.
The Status property is a pure-text string representing the user's presence information. Its value maybe be any random string, including the empty string, "".
Whenever the value in Presence or Status are changed, the component will send that information to the server. If the application or user wishes to associate a specific status message with a new presence value, it should use the ChangePresence method. ChangePresence will update both the Presence and Status properties, and then send that information to the server.
Note: It is recommended to use the ChangePresence method instead of setting this property.
This property is not available at design time.
Data Type
Integer
Resource Property (XMPP Component)
This is the resource for the current session.
Syntax
__property String Resource = { read=FResource, write=FSetResource };
Default Value
"IPWorks XMPP Agent"
Remarks
Whenever an entity logs in to an XMPP (Jabber) server, it must provide account information as well as a resource. Resources allow multiple clients to log in using the same account. The server will forward all messages and PI data aimed at a specific resource to that resource. If a command or message is to be sent to a Jabber ID with no specified resource, the server will push that command or message out to all connected resources.
Data Type
String
ServerDomain Property (XMPP Component)
The XMPP server's domain.
Syntax
__property String ServerDomain = { read=FServerDomain, write=FSetServerDomain };
Default Value
""
Remarks
The domain of the XMPP server itself. Set this value if the domain of the server is different from the DNS name of the IMServer.
Data Type
String
SSLAcceptServerCertEncoded Property (XMPP Component)
This is the certificate (PEM/base64 encoded).
Syntax
__property String SSLAcceptServerCertEncoded = { read=FSSLAcceptServerCertEncoded, write=FSetSSLAcceptServerCertEncoded }; __property DynamicArray<Byte> SSLAcceptServerCertEncodedB = { read=FSSLAcceptServerCertEncodedB, write=FSetSSLAcceptServerCertEncodedB };
Default Value
""
Remarks
This is the certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The SSLAcceptServerCertStore and SSLAcceptServerCertSubject properties also may be used to specify a certificate.
When SSLAcceptServerCertEncoded is set, a search is initiated in the current SSLAcceptServerCertStore for the private key of the certificate. If the key is found, SSLAcceptServerCertSubject is updated to reflect the full subject of the selected certificate; otherwise, SSLAcceptServerCertSubject is set to an empty string.
This property is not available at design time.
Data Type
Byte Array
SSLCertEncoded Property (XMPP Component)
This is the certificate (PEM/base64 encoded).
Syntax
__property String SSLCertEncoded = { read=FSSLCertEncoded, write=FSetSSLCertEncoded }; __property DynamicArray<Byte> SSLCertEncodedB = { read=FSSLCertEncodedB, write=FSetSSLCertEncodedB };
Default Value
""
Remarks
This is the certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The SSLCertStore and SSLCertSubject properties also may be used to specify a certificate.
When SSLCertEncoded is set, a search is initiated in the current SSLCertStore for the private key of the certificate. If the key is found, SSLCertSubject is updated to reflect the full subject of the selected certificate; otherwise, SSLCertSubject is set to an empty string.
This property is not available at design time.
Data Type
Byte Array
SSLCertStore Property (XMPP Component)
This is the name of the certificate store for the client certificate.
Syntax
__property String SSLCertStore = { read=FSSLCertStore, write=FSetSSLCertStore }; __property DynamicArray<Byte> SSLCertStoreB = { read=FSSLCertStoreB, write=FSetSSLCertStoreB };
Default Value
"MY"
Remarks
This is the name of the certificate store for the client certificate.
The SSLCertStoreType property denotes the type of the certificate store specified by SSLCertStore. If the store is password protected, specify the password in SSLCertStorePassword.
SSLCertStore is used in conjunction with the SSLCertSubject property to specify client certificates. If SSLCertStore has a value, and SSLCertSubject or SSLCertEncoded is set, a search for a certificate is initiated. Please see the SSLCertSubject property for details.
Designations of certificate stores are platform dependent.
The following designations are the most common User and Machine certificate stores in Windows:
MY | A certificate store holding personal certificates with their associated private keys. |
CA | Certifying authority certificates. |
ROOT | Root certificates. |
When the certificate store type is PFXFile, this property must be set to the name of the file. When the type is PFXBlob, the property must be set to the binary contents of a PFX file (i.e., PKCS#12 certificate store).
Data Type
Byte Array
SSLCertStorePassword Property (XMPP Component)
If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store.
Syntax
__property String SSLCertStorePassword = { read=FSSLCertStorePassword, write=FSetSSLCertStorePassword };
Default Value
""
Remarks
If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store.
Data Type
String
SSLCertStoreType Property (XMPP Component)
This is the type of certificate store for this certificate.
Syntax
__property TiotXMPPSSLCertStoreTypes SSLCertStoreType = { read=FSSLCertStoreType, write=FSetSSLCertStoreType };
enum TiotXMPPSSLCertStoreTypes { cstUser=0, cstMachine=1, cstPFXFile=2, cstPFXBlob=3, cstJKSFile=4, cstJKSBlob=5, cstPEMKeyFile=6, cstPEMKeyBlob=7, cstPublicKeyFile=8, cstPublicKeyBlob=9, cstSSHPublicKeyBlob=10, cstP7BFile=11, cstP7BBlob=12, cstSSHPublicKeyFile=13, cstPPKFile=14, cstPPKBlob=15, cstXMLFile=16, cstXMLBlob=17, cstJWKFile=18, cstJWKBlob=19, cstSecurityKey=20, cstBCFKSFile=21, cstBCFKSBlob=22, cstPKCS11=23, cstAuto=99 };
Default Value
cstUser
Remarks
This is the type of certificate store for this certificate.
The component supports both public and private keys in a variety of formats. When the cstAuto value is used, the component will automatically determine the type. This property can take one of the following values:
0 (cstUser - default) | For Windows, this specifies that the certificate store is a certificate store owned by the current user.
Note: This store type is not available in Java. |
1 (cstMachine) | For Windows, this specifies that the certificate store is a machine store.
Note: This store type is not available in Java. |
2 (cstPFXFile) | The certificate store is the name of a PFX (PKCS#12) file containing certificates. |
3 (cstPFXBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in PFX (PKCS#12) format. |
4 (cstJKSFile) | The certificate store is the name of a Java Key Store (JKS) file containing certificates.
Note: This store type is only available in Java. |
5 (cstJKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in Java Key Store (JKS) format.
Note: this store type is only available in Java. |
6 (cstPEMKeyFile) | The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate. |
7 (cstPEMKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a private key and an optional certificate. |
8 (cstPublicKeyFile) | The certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate. |
9 (cstPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a PEM- or DER-encoded public key certificate. |
10 (cstSSHPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains an SSH-style public key. |
11 (cstP7BFile) | The certificate store is the name of a PKCS#7 file containing certificates. |
12 (cstP7BBlob) | The certificate store is a string (binary) representing a certificate store in PKCS#7 format. |
13 (cstSSHPublicKeyFile) | The certificate store is the name of a file that contains an SSH-style public key. |
14 (cstPPKFile) | The certificate store is the name of a file that contains a PPK (PuTTY Private Key). |
15 (cstPPKBlob) | The certificate store is a string (binary) that contains a PPK (PuTTY Private Key). |
16 (cstXMLFile) | The certificate store is the name of a file that contains a certificate in XML format. |
17 (cstXMLBlob) | The certificate store is a string that contains a certificate in XML format. |
18 (cstJWKFile) | The certificate store is the name of a file that contains a JWK (JSON Web Key). |
19 (cstJWKBlob) | The certificate store is a string that contains a JWK (JSON Web Key). |
21 (cstBCFKSFile) | The certificate store is the name of a file that contains a BCFKS (Bouncy Castle FIPS Key Store).
Note: This store type is only available in Java and .NET. |
22 (cstBCFKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in BCFKS (Bouncy Castle FIPS Key Store) format.
Note: This store type is only available in Java and .NET. |
23 (cstPKCS11) | The certificate is present on a physical security key accessible via a PKCS#11 interface.
To use a security key, the necessary data must first be collected using the CertMgr component. The ListStoreCertificates method may be called after setting CertStoreType to cstPKCS11, CertStorePassword to the PIN, and CertStore to the full path of the PKCS#11 DLL. The certificate information returned in the CertList event's CertEncoded parameter may be saved for later use. When using a certificate, pass the previously saved security key information as the SSLCertStore and set SSLCertStorePassword to the PIN. Code Example. SSH Authentication with Security Key:
|
99 (cstAuto) | The store type is automatically detected from the input data. This setting may be used with both public and private keys and can detect any of the supported formats automatically. |
Data Type
Integer
SSLCertSubject Property (XMPP Component)
This is the subject of the certificate used for client authentication.
Syntax
__property String SSLCertSubject = { read=FSSLCertSubject, write=FSetSSLCertSubject };
Default Value
""
Remarks
This is the subject of the certificate used for client authentication.
This property must be set after all other certificate properties are set. When this property is set, a search is performed in the current certificate store to locate a certificate with a matching subject.
If a matching certificate is found, the property is set to the full subject of the matching certificate.
If an exact match is not found, the store is searched for subjects containing the value of the property.
If a match is still not found, the property is set to an empty string, and no certificate is selected.
The special value "*" picks a random certificate in the certificate store.
The certificate subject is a comma-separated list of distinguished name fields and values. For instance, "CN=www.server.com, OU=test, C=US, E=support@nsoftware.com". Common fields and their meanings are as follows:
Field | Meaning |
CN | Common Name. This is commonly a hostname like www.server.com. |
O | Organization |
OU | Organizational Unit |
L | Locality |
S | State |
C | Country |
E | Email Address |
If a field value contains a comma, it must be quoted.
Data Type
String
SSLEnabled Property (XMPP Component)
Whether TLS/SSL is enabled.
Syntax
__property bool SSLEnabled = { read=FSSLEnabled, write=FSetSSLEnabled };
Default Value
False
Remarks
This setting specifies whether TLS/SSL is enabled in the component. When False (default) the component operates in plaintext mode. When True TLS/SSL is enabled.
TLS/SSL may also be enabled by setting SSLStartMode. Setting SSLStartMode will automatically update this property value.
This property is not available at design time.
Data Type
Boolean
SSLProvider Property (XMPP Component)
This specifies the SSL/TLS implementation to use.
Syntax
__property TiotXMPPSSLProviders SSLProvider = { read=FSSLProvider, write=FSetSSLProvider };
enum TiotXMPPSSLProviders { sslpAutomatic=0, sslpPlatform=1, sslpInternal=2 };
Default Value
sslpAutomatic
Remarks
This property specifies the SSL/TLS implementation to use. In most cases the default value of 0 (Automatic) is recommended and should not be changed. When set to 0 (Automatic) the component will select whether to use the platform implementation or the internal implementation depending on the operating system as well as the TLS version being used.
Possible values are:
0 (sslpAutomatic - default) | Automatically selects the appropriate implementation. |
1 (sslpPlatform) | Uses the platform/system implementation. |
2 (sslpInternal) | Uses the internal implementation. |
In most cases using the default value (Automatic) is recommended. The component will select a provider depending on the current platform.
When Automatic is selected the platform implementation is used by default. When TLS 1.3 is enabled via SSLEnabledProtocols the internal implementation is used.
Data Type
Integer
SSLServerCertEncoded Property (XMPP Component)
This is the certificate (PEM/base64 encoded).
Syntax
__property String SSLServerCertEncoded = { read=FSSLServerCertEncoded }; __property DynamicArray<Byte> SSLServerCertEncodedB = { read=FSSLServerCertEncodedB };
Default Value
""
Remarks
This is the certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The SSLServerCertStore and SSLServerCertSubject properties also may be used to specify a certificate.
When SSLServerCertEncoded is set, a search is initiated in the current SSLServerCertStore for the private key of the certificate. If the key is found, SSLServerCertSubject is updated to reflect the full subject of the selected certificate; otherwise, SSLServerCertSubject is set to an empty string.
This property is read-only and not available at design time.
Data Type
Byte Array
SSLStartMode Property (XMPP Component)
Determines how the component starts the SSL negotiation.
Syntax
__property TiotXMPPSSLStartModes SSLStartMode = { read=FSSLStartMode, write=FSetSSLStartMode };
enum TiotXMPPSSLStartModes { sslAutomatic=0, sslImplicit=1, sslExplicit=2, sslNone=3 };
Default Value
sslNone
Remarks
The SSLStartMode property may have one of the following values:
0 (sslAutomatic) | If the remote port is set to the standard plaintext port of the protocol (where applicable), the component will behave the same as if SSLStartMode is set to sslExplicit. In all other cases, SSL negotiation will be implicit (sslImplicit). |
1 (sslImplicit) | The SSL negotiation will start immediately after the connection is established. |
2 (sslExplicit) | The component will first connect in plaintext, and then explicitly start SSL negotiation through a protocol command such as STARTTLS. |
3 (sslNone - default) | No SSL negotiation, no SSL security. All communication will be in plaintext mode. |
Data Type
Integer
Status Property (XMPP Component)
Description of the availability of this entity.
Syntax
__property String Status = { read=FStatus, write=FSetStatus };
Default Value
"Available for Chat."
Remarks
When the component completes the initial log in, it will send information telling other entities subscribed to this entity's presence that it is online. The application must provide different status and availability information as the user changes them.
The Presence property has one of four values representing general information about the user's status as defined in the Jabber protocol specification:
pcOffline (0) | Invisible: JabberId is offline. |
pcChat (1) | Available: JabberId is online. |
pcAway (2) | Away: JabberId is online, but the user is away from their computer. |
pcXA (3) | Extended Away: JabberId is online, but the user is away from their computer for an extended period of time. |
pcDND (4) | Do not Disturb: JabberId is online, but is busy and does not wish to be disturbed. |
By default, the component sets the client presence to pcChat, meaning that the user is available. To change the initial status sent by the component set Presence to the desired presence before calling Connect.
Note: offline is not officially supported by the XMPP specification, however some XMPP server implementations may recognize the value. Setting the client's presence state to this value may cause the server to respond with an Error.
The Status property is a pure-text string representing the user's presence information. Its value maybe be any random string, including the empty string, "".
Whenever the value in Presence or Status are changed, the component will send that information to the server. If the application or user wishes to associate a specific status message with a new presence value, it should use the ChangePresence method. ChangePresence will update both the Presence and Status properties, and then send that information to the server.
Note: It is recommended to use the ChangePresence method instead of setting this property.
This property is not available at design time.
Data Type
String
Timeout Property (XMPP Component)
A timeout for the component.
Syntax
__property int Timeout = { read=FTimeout, write=FSetTimeout };
Default Value
60
Remarks
If the Timeout property is set to 0, all operations will run uninterrupted until successful completion or an error condition is encountered.
If Timeout is set to a positive value, the component will wait for the operation to complete before returning control.
The component will use DoEvents to enter an efficient wait loop during any potential waiting period, making sure that all system events are processed immediately as they arrive. This ensures that the host application does not "freeze" and remains responsive.
If Timeout expires, and the operation is not yet complete, the component raises an exception.
Please note that by default, all timeouts are inactivity timeouts, i.e. the timeout period is extended by Timeout seconds when any amount of data is successfully sent or received.
The default value for the Timeout property is 60 seconds.
Data Type
Integer
User Property (XMPP Component)
The user portion of this entity's Jabber ID.
Syntax
__property String User = { read=FUser, write=FSetUser };
Default Value
""
Remarks
The User property is a unique username associated with this entity and set at time of registration under the field "user".
Data Type
String
UserDomain Property (XMPP Component)
Gets or sets the domain value used for Jabber IDs.
Syntax
__property String UserDomain = { read=FUserDomain, write=FSetUserDomain };
Default Value
""
Remarks
A Jabber ID (JID) is a unique identifier of the format "User@Domain/Resource". user@domain denotes the account by username and domain. The Resource is given during the login process to distinguish individual connections under the same account. If the IMServer contains multiple domains, this property setting allows the user to specify the domain under which to login.
If Domain is empty, the value in IMServer is used by default when creating the client's JID.
Data Type
String
UserInfoCount Property (XMPP Component)
The number of records in the UserInfo arrays.
Syntax
__property int UserInfoCount = { read=FUserInfoCount, write=FSetUserInfoCount };
Default Value
0
Remarks
This property controls the size of the following arrays:
The array indices start at 0 and end at UserInfoCount - 1.This property is not available at design time.
Data Type
Integer
UserInfoField Property (XMPP Component)
This is the name of the current property necessary for registration.
Syntax
__property String UserInfoField[int FieldIndex] = { read=FUserInfoField, write=FSetUserInfoField };
Default Value
""
Remarks
This is the name of the current property necessary for registration.
Before a registration can be attempted, the application should use the QueryRegister method to poll the host to which the user wishes to register. This will gather all of the necessary fields that the user must send to the server, and will populate the UserInfo properties accordingly. After a successful query, all entries in UserInfo values will be empty strings.
The possible registration fields are defined in the Jabber protocol specification as follows:
instructions | Special instructions sent from the server. |
username | The username to be associated with this account. |
password | The initial password for this account. |
name | The user's name. |
The user's email address. | |
address | The user's physical address. |
city | The user's city of residence. |
state | The user's state (for United States citizens). |
zip | The user's postal code (for United States citizens). |
phone | The user's phone number. |
URL | The user's website. |
date | The date of registration. |
misc | Any miscellaneous data. |
text | Any extra text (potentially for a personal bio). |
remove | Specifies a request to unregister. |
After the user has set all of the values in UserInfo, and added any extra fields they may wish to include in their registration, the application should make a call to Register.
If the component is not already connected when this method is called, it will connect, poll the registration fields, and then disconnect.
The FieldIndex parameter specifies the index of the item in the array. The size of the array is controlled by the UserInfoCount property.
This property is not available at design time.
Data Type
String
UserInfoValue Property (XMPP Component)
This is the value for the current registration property, and should be set after calling QueryRegister and before calling Register .
Syntax
__property String UserInfoValue[int FieldIndex] = { read=FUserInfoValue, write=FSetUserInfoValue };
Default Value
""
Remarks
This is the value for the current registration field, and should be set after calling QueryRegister and before calling Register.
Before a registration can be attempted, the application should use the QueryRegister method to poll the host to which the user wishes to register. This will gather all of the necessary fields that the user must send to the server, and will populate the UserInfo properties accordingly. After a successful query, all entries in UserInfo values will be empty strings.
The possible registration fields are defined in the Jabber protocol specification as follows:
instructions | Special instructions sent from the server. |
username | The username to be associated with this account. |
password | The initial password for this account. |
name | The user's name. |
The user's email address. | |
address | The user's physical address. |
city | The user's city of residence. |
state | The user's state (for United States citizens). |
zip | The user's postal code (for United States citizens). |
phone | The user's phone number. |
URL | The user's website. |
date | The date of registration. |
misc | Any miscellaneous data. |
text | Any extra text (potentially for a personal bio). |
remove | Specifies a request to unregister. |
After the user has set all of the values in UserInfo, and added any extra fields they may wish to include in their registration, the application should make a call to Register.
If the component is not already connected when this method is called, it will connect, poll the registration fields, and then disconnect.
The FieldIndex parameter specifies the index of the item in the array. The size of the array is controlled by the UserInfoCount property.
This property is not available at design time.
Data Type
String
Add Method (XMPP Component)
This method will add an entity to this entity's roster.
Syntax
void __fastcall Add(String JabberId, String Name, String Groups);
Remarks
JabberId is the Jabber ID of the entity to be added. It should be of form "user@host". If no hostname is specified, the component will assume the user's account is with the server in IMServer, and will append that hostname to JabberId before sending the request.
Name will contain the name that is to be associated with JabberId in this entity's roster. It may be the empty string, "".
Groups is either the empty string ("") or a comma- separated list of groups to which JabberId is to be added. If JabberId already exists in the buddy list, it will be updated to exist only in the specified groups. A buddy's group list can also be modified by the Buddies property.
The Add method will make a subscription request to the presence of the specified JabberId. Upon receiving this request, the server will add an entry into this user's buddy list with a subscription of type subscriptionNone (0) if there was no previous entry (if this user has already allowed JabberId to subscribe to this user's presence, there will already be an entry of type subscriptionFrom (2)). If the contact chooses to allow the subscription, the server will update the entry and a BuddyUpdate event will fire with the new subscription value (subscriptionTo (1) if this is a new contact, or subscriptionBoth (3) if the contact is now mutual).
The XMPP protocol permits XMPP (Jabber) clients to communicate with foreign IM networks such as AIM, MSN, SMS, and others through the use of gateway servers that translate between the foreign protocol and XMPP. When sending or receiving presence information, messages, or subscription requests, Domain will be a gateway for the foreign network on which the contact resides and with which this user has registered an account for that foreign network. The Register method can be used to register with a foreign network gateway.
Cancel Method (XMPP Component)
This will cancel another entity's subscription to this entity's presence.
Syntax
void __fastcall Cancel(String JabberId);
Remarks
If for any reason the user should want to undo a previously granted subscription, this can be achieved through the Cancel method. The method will unsubscribe the target from this user's presence, thus preventing the target from seeing this user in the future.
ChangePassword Method (XMPP Component)
This method will change the current user's password.
Syntax
void __fastcall ChangePassword(String Password);
Remarks
This method changes the current user's password to the password that is specified. The component must be connected to the server when this method is called.
ChangePresence Method (XMPP Component)
This method will set the availability and status of this entity.
Syntax
void __fastcall ChangePresence(int PresenceCode, String Status);
Remarks
PresenceCode should correspond the possible values of the Presence property:
pcOffline (0) | Invisible: JabberId is offline. |
pcChat (1) | Available: JabberId is online. |
pcAway (2) | Away: JabberId is online, but the user is away from their computer. |
pcXA (3) | Extended Away: JabberId is online, but the user is away from their computer for an extended period of time. |
pcDND (4) | Do not Disturb: JabberId is online, but is busy and does not wish to be disturbed. |
By default, the component sets the client presence to pcChat, meaning that the user is available. To change the initial status sent by the component set Presence to the desired presence before calling Connect.
Note: offline is not officially supported by the XMPP specification, however some XMPP server implementations may recognize the value. Setting the client's presence state to this value may cause the server to respond with an Error.
Status can be any random string, including the empty string "".
Config Method (XMPP Component)
Sets or retrieves a configuration setting.
Syntax
String __fastcall Config(String ConfigurationString);
Remarks
Config is a generic method available in every component. It is used to set and retrieve configuration settings for the component.
These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.
To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).
To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.
Connect Method (XMPP Component)
This method will connect the component to the server.
Syntax
void __fastcall Connect();
Remarks
The Connect method performs the entire connection routine. This includes connection to the IMServer, authenticating with the specified User and Password, and session initialization.
The Connected event will fire once for the initial TCP connection and again when the XMPP Logon is complete.
ConnectTo Method (XMPP Component)
This method will connect the component to the server.
Syntax
void __fastcall ConnectTo(String User, String Password);
Remarks
The ConnectTo method performs the entire connection routine. This includes connection to the IMServer, user logon and authentication, and session initialization.
The Connected event will fire once for the initial TCP connection and again when the XMPP Logon is complete.
Since ConnectTo is called with a user and password specified, the User and Password properties will updated accordingly.
Disconnect Method (XMPP Component)
This method disconnects the component from the server.
Syntax
void __fastcall Disconnect();
Remarks
The Disconnect method will send the disconnect command to the notification server. Upon disconnection, a Disconnected event will be fired.
DoEvents Method (XMPP Component)
This method processes events from the internal message queue.
Syntax
void __fastcall DoEvents();
Remarks
When DoEvents is called, the component processes any available events. If no events are available, it waits for a preset period of time, and then returns.
Interrupt Method (XMPP Component)
Interrupt the current method.
Syntax
void __fastcall Interrupt();
Remarks
If there is no method in progress, Interrupt simply returns, doing nothing.
ProbePresence Method (XMPP Component)
Use this method to probe for another entity's presence.
Syntax
void __fastcall ProbePresence(String JabberId);
Remarks
In the case that the user needs to update a particular entity's presence this method can be used to retrieve it. After a successful call, the server will either respond with the last known presence for Jabber, or will send a presence element of type "error". In either case, the respond will be returned by a Presence event.
QueryRegister Method (XMPP Component)
This method queries a server for the necessary registration fields.
Syntax
void __fastcall QueryRegister(String XMPPServer);
Remarks
Before a registration can be attempted, the application should use the QueryRegister method to poll the host to which the user wishes to register. This will gather all of the necessary fields that the user must send to the server, and will populate the UserInfo properties accordingly. After a successful query, all entries in UserInfo values will be empty strings.
The possible registration fields are defined in the Jabber protocol specification as follows:
instructions | Special instructions sent from the server. |
username | The username to be associated with this account. |
password | The initial password for this account. |
name | The user's name. |
The user's email address. | |
address | The user's physical address. |
city | The user's city of residence. |
state | The user's state (for United States citizens). |
zip | The user's postal code (for United States citizens). |
phone | The user's phone number. |
URL | The user's website. |
date | The date of registration. |
misc | Any miscellaneous data. |
text | Any extra text (potentially for a personal bio). |
remove | Specifies a request to unregister. |
After the user has set all of the values in UserInfo, and added any extra fields they may wish to include in their registration, the application should make a call to Register.
If the component is not already connected when this method is called, it will connect, poll the registration fields, and then disconnect.
Register Method (XMPP Component)
This method registers an account with a server.
Syntax
void __fastcall Register(String XMPPServer);
Remarks
Before a registration can be attempted, the application should use the QueryRegister method to poll the host to which the user wishes to register. This will gather all of the necessary fields that the user must send to the server, and will populate the UserInfo properties accordingly. After a successful query, all entries in UserInfo values will be empty strings.
The possible registration fields are defined in the Jabber protocol specification as follows:
instructions | Special instructions sent from the server. |
username | The username to be associated with this account. |
password | The initial password for this account. |
name | The user's name. |
The user's email address. | |
address | The user's physical address. |
city | The user's city of residence. |
state | The user's state (for United States citizens). |
zip | The user's postal code (for United States citizens). |
phone | The user's phone number. |
URL | The user's website. |
date | The date of registration. |
misc | Any miscellaneous data. |
text | Any extra text (potentially for a personal bio). |
remove | Specifies a request to unregister. |
After the user has set all of the values in UserInfo, and added any extra fields they may wish to include in their registration, the application should make a call to Register.
If the component is not already connected when this method is called, it will connect, poll the registration fields, and then disconnect.
A new account can be registered at any time, including while the component is logged into the host under an existing account.
Remove Method (XMPP Component)
This method will remove an entity from this entity's roster.
Syntax
void __fastcall Remove(String JabberId, String Name, String Group);
Remarks
JabberId is the Jabber ID of the entity to be removed. It should be of form "user@host". If no hostname is specified, the component will assume the user's account is with the server in IMServer, and will append that hostname to JabberId before sending the request.
Name should contain the name that is to be associated with JabberId in this entity's roster. It may be the empty string, "".
Groups may be either the empty string ("") or a comma- separated list of groups from which JabberId is to be removed. If no group is specified, the buddy will be completely removed from the buddy list.
After calling the Remove method, the server will remove the entry from the server-side roster, and will push the result out to all connected resources. A BuddyUpdate event will fire with subscription of type subscriptionRemove, and the entry will be removed from the Jabber component's internally stored list.
Reset Method (XMPP Component)
Reset the component.
Syntax
void __fastcall Reset();
Remarks
This method will reset the component's properties to their default values.
RetrieveRoster Method (XMPP Component)
This method will retrieve this entity's roster from the server.
Syntax
void __fastcall RetrieveRoster();
Remarks
After the component connects, it will automatically send a request to the server to retrieve the roster. However, should the user or application wish to update the entire roster, this method may be used to do so.
After a successful call to the RetrieveRoster method, the server will respond with this entity's roster. The component will parse the roster and fire the Sync event once per item. This event may also fire for each entity added to or removed from the roster.
SendCommand Method (XMPP Component)
This method sends a command to the server.
Syntax
void __fastcall SendCommand(String Command);
Remarks
The SendCommand method will send the Command parameter to the server. The command must be in valid XML format, and must be recognizable to the IMServer.
The SendCommand method should only be used by programmers or users who are connecting to non-standard servers whose command list is not covered by the component. Any responses that are defined in the protocol specification will be returned by the appropriate event. Any non-standard IQ message will be returned by the IQ event. All other responses will be returned by the PITrail event.
SendFile Method (XMPP Component)
Sends a file to the specified user.
Syntax
void __fastcall SendFile(String JabberId);
Remarks
This method sends the file specified by LocalFile to the user specified by the JabberId parameter.
JabberId is the intended recipient of the message. It is of the form user@domain/resource. If a resource is not supplied, all logged-in instances of the user's account will receive the message.
The component supports sending files using In-Band Bystestreams as defined in XEP-0047 and XEP-0096.
SendMsg Method (XMPP Component)
This method will send a message to the specified user.
Syntax
String __fastcall SendMsg(String JabberId);
Remarks
SetUserInfoField Method (XMPP Component)
This method will add a user information field for registration.
Syntax
void __fastcall SetUserInfoField(String Field, String Value);
Remarks
This method will search through UserInfo for the field name in Field and set the corresponding value to Value. If the field was not previously contained in UserInfo, it will automatically added.
Before a registration can be attempted, the application should use the QueryRegister method to poll the host to which the user wishes to register. This will gather all of the necessary fields that the user must send to the server, and will populate the UserInfo properties accordingly. After a successful query, all entries in UserInfo values will be empty strings.
The possible registration fields are defined in the Jabber protocol specification as follows:
instructions | Special instructions sent from the server. |
username | The username to be associated with this account. |
password | The initial password for this account. |
name | The user's name. |
The user's email address. | |
address | The user's physical address. |
city | The user's city of residence. |
state | The user's state (for United States citizens). |
zip | The user's postal code (for United States citizens). |
phone | The user's phone number. |
URL | The user's website. |
date | The date of registration. |
misc | Any miscellaneous data. |
text | Any extra text (potentially for a personal bio). |
remove | Specifies a request to unregister. |
After the user has set all of the values in UserInfo, and added any extra fields they may wish to include in their registration, the application should make a call to Register.
If the component is not already connected when this method is called, it will connect, poll the registration fields, and then disconnect.
SubscribeTo Method (XMPP Component)
Use this method to subscribe to another entity's presence.
Syntax
void __fastcall SubscribeTo(String JabberId);
Remarks
This method will send a request for a subscription to JabberId's presence. If the entity allows the subscription, a new item will be stored in the buddy list with the appropriate subscription type. Otherwise, no change will take place.
Unregister Method (XMPP Component)
This method cancels an account with the host.
Syntax
void __fastcall Unregister();
Remarks
If the user or application wishes to terminate an account with the IMServer it should make a call to this method. After a successful call, the account will be canceled and the component will be logged off the server, but not disconnected.
UnsubscribeTo Method (XMPP Component)
This method will cancel a subscription to another entity's presence.
Syntax
void __fastcall UnsubscribeTo(String JabberId);
Remarks
This method will inform the server of the cancellation of subscription to JabberId's presence. After a successful call the subscription type of the associated buddy list item will be updated.
UpdateBuddyGroup Method (XMPP Component)
Updates the buddy's associatd groups.
Syntax
void __fastcall UpdateBuddyGroup(int BuddyIndex, String Group);
Remarks
This method updates the associated groups for the buddy specified by BuddyIndex.
After the Sync event has fired the BuddyGroup property is populated with a comma-separated list of groups for each buddy. To update the groups for a buddy call this method with the buddy's index and the comma-separate list of groups the buddy should be associated with. Setting Group to empty string ("") will cause the buddy to be completely disassociated from all groups.
BuddyUpdate Event (XMPP Component)
This event is fired whenever a roster entry is updated.
Syntax
typedef struct { int BuddyIdx; } TiotXMPPBuddyUpdateEventParams; typedef void __fastcall (__closure *TiotXMPPBuddyUpdateEvent)(System::TObject* Sender, TiotXMPPBuddyUpdateEventParams *e); __property TiotXMPPBuddyUpdateEvent OnBuddyUpdate = { read=FOnBuddyUpdate, write=FOnBuddyUpdate };
Remarks
The BuddyUpdate event will fire whenever a new buddy list entry is added or an old entry is updated. The updated information can be retrieved through the Buddies properties property. The BuddyIdx parameter of this event will be the index of that XMPPBuddy in the properties.
Connected Event (XMPP Component)
This event is fired when a connection to the IM Server is completed.
Syntax
typedef struct { int StatusCode; String Description; } TiotXMPPConnectedEventParams; typedef void __fastcall (__closure *TiotXMPPConnectedEvent)(System::TObject* Sender, TiotXMPPConnectedEventParams *e); __property TiotXMPPConnectedEvent OnConnected = { read=FOnConnected, write=FOnConnected };
Remarks
If the connection is made normally, StatusCode is 0, and Description is "OK".
If the connection fails, StatusCode has the error code returned by the TCP/IP stack. Description contains a description of this code. The value of StatusCode is equal to the value of the error.
Please refer to the Error Codes section for more information.
ConnectionStatus Event (XMPP Component)
This event is fired to indicate changes in the connection state.
Syntax
typedef struct { String ConnectionEvent; int StatusCode; String Description; } TiotXMPPConnectionStatusEventParams; typedef void __fastcall (__closure *TiotXMPPConnectionStatusEvent)(System::TObject* Sender, TiotXMPPConnectionStatusEventParams *e); __property TiotXMPPConnectionStatusEvent OnConnectionStatus = { read=FOnConnectionStatus, write=FOnConnectionStatus };
Remarks
The ConnectionStatus event is fired when the connection state changes: for example, completion of a firewall or proxy connection or completion of a security handshake.
The ConnectionEvent parameter indicates the type of connection event. Values may include the following:
Firewall connection complete. | |
Secure Sockets Layer (SSL) or S/Shell handshake complete (where applicable). | |
Remote host connection complete. | |
Remote host disconnected. | |
SSL or S/Shell connection broken. | |
Firewall host disconnected. |
Disconnected Event (XMPP Component)
This event is fired when the chat service connection is lost.
Syntax
typedef struct { int StatusCode; String Description; } TiotXMPPDisconnectedEventParams; typedef void __fastcall (__closure *TiotXMPPDisconnectedEvent)(System::TObject* Sender, TiotXMPPDisconnectedEventParams *e); __property TiotXMPPDisconnectedEvent OnDisconnected = { read=FOnDisconnected, write=FOnDisconnected };
Remarks
If the connection is broken normally, StatusCode is 0, and Description is "OK".
If the connection is broken for any other reason, StatusCode has the error code returned by the TCP/IP subsystem. Description contains a description of this code. The value of StatusCode is equal to the value of the TCP/IP error.
Please refer to the Error Codes section for more information.
EndTransfer Event (XMPP Component)
Fired when a file transfer completes.
Syntax
typedef struct { int Direction; String FileId; String Filename; bool Success; } TiotXMPPEndTransferEventParams; typedef void __fastcall (__closure *TiotXMPPEndTransferEvent)(System::TObject* Sender, TiotXMPPEndTransferEventParams *e); __property TiotXMPPEndTransferEvent OnEndTransfer = { read=FOnEndTransfer, write=FOnEndTransfer };
Remarks
When a file transfer completes this event will fire.
The Direction parameter shows whether the client (0) or the server (1) is sending the data.
Error Event (XMPP Component)
This event is fired when the server sends a protocol error message.
Syntax
typedef struct { int ErrorCode; String Description; } TiotXMPPErrorEventParams; typedef void __fastcall (__closure *TiotXMPPErrorEvent)(System::TObject* Sender, TiotXMPPErrorEventParams *e); __property TiotXMPPErrorEvent OnError = { read=FOnError, write=FOnError };
Remarks
This is fired whenever there is a protocol error. ErrorCode will contain the error code string sent by the server. Description will contain the Xmpp component's interpretation of the code.
IQ Event (XMPP Component)
This event is fired for IQ messages not normally supported by the component.
Syntax
typedef struct { String Iq; String Id; String From; String IqType; bool Ignore; } TiotXMPPIQEventParams; typedef void __fastcall (__closure *TiotXMPPIQEvent)(System::TObject* Sender, TiotXMPPIQEventParams *e); __property TiotXMPPIQEvent OnIQ = { read=FOnIQ, write=FOnIQ };
Remarks
Some servers may wish to gather some data from the client in ways not specified by the XMPP RFC. This event will contain any IQ message that is not a part of the Jabber specification. The Iq parameter will contain an entire XML entity, and thus will require both knowledge of XML and knowledge of the possible contents of the IQ message to parse. Id will contain the transaction id of the IQ message. From will contain the sender's Jabber ID. IqType will have one of the following values:
"get" | The IQ is requesting information from this XMPP client. |
"set" | The IQ is attempting to set a value.. |
"result" | The IQ is a success response to a previous IQ. |
"error" | The IQ is an error response to a previous IQ. |
Note: to respond to these IQs, you may use the SendCommand method.
MessageIn Event (XMPP Component)
This event is fired upon receipt of a message.
Syntax
typedef struct { String MessageId; String From; String Domain; String Resource; int MessageType; String Subject; String MessageThread; String MessageText; String MessageHTML; String Other; } TiotXMPPMessageInEventParams; typedef void __fastcall (__closure *TiotXMPPMessageInEvent)(System::TObject* Sender, TiotXMPPMessageInEventParams *e); __property TiotXMPPMessageInEvent OnMessageIn = { read=FOnMessageIn, write=FOnMessageIn };
Remarks
When a message is received, the XMPP component will parse the sender's Jabber ID into the From, Domain, and Resource fields. These parameters can be used to track the exact instance of a user's account that originated the message.
MessageId can be used with Jabber extension protocols. The MessageText parameter is the plaintext portion of the message body. MessageHTML will contain any HTML from the message.
Type the type of message received. See MessageType for a list of possible values. For message of type "headline", Subject will reflect the subject of the message. For messages of type "chat", Thread will report the conversation thread for which the current message is a follow-up.
Other will contains any extra data associated with the message but not defined by the XMPP-IM protocol.
PITrail Event (XMPP Component)
This event is fired for all protocol messages.
Syntax
typedef struct { int Direction; String Pi; } TiotXMPPPITrailEventParams; typedef void __fastcall (__closure *TiotXMPPPITrailEvent)(System::TObject* Sender, TiotXMPPPITrailEventParams *e); __property TiotXMPPPITrailEvent OnPITrail = { read=FOnPITrail, write=FOnPITrail };
Remarks
The PITrail event is useful for debugging purposes. It shows all the interaction between the client and the server, line by line.
SessionId will hold the session number that originated the PI. A value of 0 is reserved for all PI dealing with the IMServer.
The direction parameter shows the originator of the message:
0 (Client) | Pi originates from the client. |
1 (Server) | Pi originates from the server. |
2 (Info) | Pi is an informative message originating from within the component. |
The Pi parameter contains the PI message.
Presence Event (XMPP Component)
This event is fired when the presence of a subscribed entity changes.
Syntax
typedef struct { String User; String Domain; String Resource; int Availability; String Status; } TiotXMPPPresenceEventParams; typedef void __fastcall (__closure *TiotXMPPPresenceEvent)(System::TObject* Sender, TiotXMPPPresenceEventParams *e); __property TiotXMPPPresenceEvent OnPresence = { read=FOnPresence, write=FOnPresence };
Remarks
This event contains the availability and status information of a particular Jabber entity to whom this entity has a subscription.
Because a user can log in multiple times using the same account, the XMPP component will parse the user's Jabber ID into the User, Domain and Resource parameters so that the client can easily track which instance of the account sent the presence.
The XMPP protocol permits XMPP (Jabber) clients to communicate with foreign IM networks such as AIM, MSN, SMS, and others through the use of gateway servers that translate between the foreign protocol and XMPP. When sending or receiving presence information, messages, or subscription requests, Domain will be a gateway for the foreign network on which the contact resides and with which this user has registered an account for that foreign network. The Register method can be used to register with a foreign network gateway.
Availability corresponds to the Presence property of the component, with the same possible values:
pcOffline (0) | Invisible: JabberId is offline. |
pcChat (1) | Available: JabberId is online. |
pcAway (2) | Away: JabberId is online, but the user is away from their computer. |
pcXA (3) | Extended Away: JabberId is online, but the user is away from their computer for an extended period of time. |
pcDND (4) | Do not Disturb: JabberId is online, but is busy and does not wish to be disturbed. |
By default, the component sets the client presence to pcChat, meaning that the user is available. To change the initial status sent by the component set Presence to the desired presence before calling Connect.
Note: offline is not officially supported by the XMPP specification, however some XMPP server implementations may recognize the value. Setting the client's presence state to this value may cause the server to respond with an Error.
Status corresponds to the Status property. This value may be any random string, including the empty string, "".
ReadyToSend Event (XMPP Component)
This event is fired when the component is ready to send data.
Syntax
typedef struct { } TiotXMPPReadyToSendEventParams; typedef void __fastcall (__closure *TiotXMPPReadyToSendEvent)(System::TObject* Sender, TiotXMPPReadyToSendEventParams *e); __property TiotXMPPReadyToSendEvent OnReadyToSend = { read=FOnReadyToSend, write=FOnReadyToSend };
Remarks
The ReadyToSend event indicates that the underlying Transmission Control Protocol (TCP)/IP subsystem is ready to accept data after a failed DataToSend. This event also is fired immediately after a connection to the remote host is established.
SSLServerAuthentication Event (XMPP Component)
Fired after the server presents its certificate to the client.
Syntax
typedef struct { String CertEncoded; DynamicArray<Byte> CertEncodedB; String CertSubject; String CertIssuer; String Status; bool Accept; } TiotXMPPSSLServerAuthenticationEventParams; typedef void __fastcall (__closure *TiotXMPPSSLServerAuthenticationEvent)(System::TObject* Sender, TiotXMPPSSLServerAuthenticationEventParams *e); __property TiotXMPPSSLServerAuthenticationEvent OnSSLServerAuthentication = { read=FOnSSLServerAuthentication, write=FOnSSLServerAuthentication };
Remarks
During this event, the client can decide whether or not to continue with the connection process. The Accept parameter is a recommendation on whether to continue or close the connection. This is just a suggestion: application software must use its own logic to determine whether or not to continue.
When Accept is False, Status shows why the verification failed (otherwise, Status contains the string OK). If it is decided to continue, you can override and accept the certificate by setting the Accept parameter to True.
SSLStatus Event (XMPP Component)
Shows the progress of the secure connection.
Syntax
typedef struct { String Message; } TiotXMPPSSLStatusEventParams; typedef void __fastcall (__closure *TiotXMPPSSLStatusEvent)(System::TObject* Sender, TiotXMPPSSLStatusEventParams *e); __property TiotXMPPSSLStatusEvent OnSSLStatus = { read=FOnSSLStatus, write=FOnSSLStatus };
Remarks
The event is fired for informational and logging purposes only. This event tracks the progress of the connection.
StartTransfer Event (XMPP Component)
Fired when a file transfer begins.
Syntax
typedef struct { int Direction; String FileId; String User; String Domain; String Resource; String Filename; String Datetime; __int64 Size; bool Accept; } TiotXMPPStartTransferEventParams; typedef void __fastcall (__closure *TiotXMPPStartTransferEvent)(System::TObject* Sender, TiotXMPPStartTransferEventParams *e); __property TiotXMPPStartTransferEvent OnStartTransfer = { read=FOnStartTransfer, write=FOnStartTransfer };
Remarks
When a file is received, the XMPP component will parse the sender's Jabber ID into the User, Domain, and Resource fields. The FileId and Filename parameters identify the current transfer. Within this event you may override the Filename by setting the Filename parameter. At this time you may also set LocalDirectory if it is not already set.
When a sending a file, the XMPP component will parse the receiver's Jabber ID into the User, Domain, and Resource fields.
The Direction parameter shows whether the client (0) or the server (1) is sending the data.
SubscriptionRequest Event (XMPP Component)
This event fires when a subscription request is received.
Syntax
typedef struct { String From; String Domain; bool Accept; } TiotXMPPSubscriptionRequestEventParams; typedef void __fastcall (__closure *TiotXMPPSubscriptionRequestEvent)(System::TObject* Sender, TiotXMPPSubscriptionRequestEventParams *e); __property TiotXMPPSubscriptionRequestEvent OnSubscriptionRequest = { read=FOnSubscriptionRequest, write=FOnSubscriptionRequest };
Remarks
This event fires whenever another XMPP entity requests a subscription to this entity's presence. The XMPP component will parse the requesting entity's Jabber ID into the From and Domain parameters. There is no need to know which resource sent the request, since all instances of the requesting entity's account have access to the same roster.
Accept will initially be false, but setting it to true will cause the XMPP component to allow the remote subscription. Otherwise, the XMPP component will actively deny the subscription request.
Sync Event (XMPP Component)
This event fires upon a complete information synchronization with the server.
Syntax
typedef struct { } TiotXMPPSyncEventParams; typedef void __fastcall (__closure *TiotXMPPSyncEvent)(System::TObject* Sender, TiotXMPPSyncEventParams *e); __property TiotXMPPSyncEvent OnSync = { read=FOnSync, write=FOnSync };
Remarks
The Sync event will fire after each successful call to the RetrieveRoster method. When the event fires, the buddy list, or roster, will be completely retrieved and the Buddies properties will be filled out accordingly:
Id | the jabber ids associated with the buddies |
Group | the group associated with each entry (if a buddy is in more than one group, they will have multiple entries in the buddy list) |
Subscription | the subscription type for each buddy |
Please refer to Buddies properties property for more information.
Transfer Event (XMPP Component)
Fired during file transfer.
Syntax
typedef struct { int Direction; String FileId; String Filename; __int64 BytesTransferred; int PercentDone; String Text; DynamicArray<Byte> TextB; bool Cancel; } TiotXMPPTransferEventParams; typedef void __fastcall (__closure *TiotXMPPTransferEvent)(System::TObject* Sender, TiotXMPPTransferEventParams *e); __property TiotXMPPTransferEvent OnTransfer = { read=FOnTransfer, write=FOnTransfer };
Remarks
This event will fire when sending or receiving. One or more Transfer events are fired during file transfer.
The BytesTransferred parameter shows the number of bytes transferred since the beginning of the transfer.
Text contains the portion of the file data being delivered.
The Direction parameter shows whether the client (0) or the server (1) is sending the data.
The PercentDone parameter shows the progress of the transfer in the corresponding direction. If PercentDone can not be calculated the value will be -1.
The Direction parameter shows whether the client (0) or the server (1) is sending the data.
The PercentDone parameter shows the progress of the transfer in the corresponding direction. If PercentDone can not be calculated the value will be -1.
Note: Events are not re-entrant. Performing time-consuming operations within this event will prevent it from firing again in a timely manner and may affect overall performance.
Config Settings (XMPP Component)
The component accepts one or more of the following configuration settings. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.XMPP Config Settings
TCPClient Config Settings
If the FirewallHost setting is set to a Domain Name, a DNS request is initiated. Upon successful termination of the request, the FirewallHost setting is set to the corresponding address. If the search is not successful, an error is returned.
Note: This setting is provided for use by components that do not directly expose Firewall properties.
Note: This setting is provided for use by components that do not directly expose Firewall properties.
Note: This configuration setting is provided for use by components that do not directly expose Firewall properties.
0 | No firewall (default setting). |
1 | Connect through a tunneling proxy. FirewallPort is set to 80. |
2 | Connect through a SOCKS4 Proxy. FirewallPort is set to 1080. |
3 | Connect through a SOCKS5 Proxy. FirewallPort is set to 1080. |
10 | Connect through a SOCKS4A Proxy. FirewallPort is set to 1080. |
Note: This setting is provided for use by components that do not directly expose Firewall properties.
Note: This setting is provided for use by components that do not directly expose Firewall properties.
Note: This value is not applicable in macOS.
In the case that Linger is True (default), two scenarios determine how long the connection will linger. In the first, if LingerTime is 0 (default), the system will attempt to send pending data for a connection until the default IP timeout expires.
In the second scenario, if LingerTime is a positive value, the system will attempt to send pending data until the specified LingerTime is reached. If this attempt fails, then the system will reset the connection.
The default behavior (which is also the default mode for stream sockets) might result in a long delay in closing the connection. Although the component returns control immediately, the system could hold system resources until all pending data are sent (even after your application closes).
Setting this property to False forces an immediate disconnection. If you know that the other side has received all the data you sent (e.g., by a client acknowledgment), setting this property to False might be the appropriate course of action.
In multi-homed hosts (machines with more than one IP interface) setting LocalHost to the value of an interface will make the component initiate connections (or accept in the case of server components) only through that interface.
If the component is connected, the LocalHost setting shows the IP address of the interface through which the connection is made in internet dotted format (aaa.bbb.ccc.ddd). In most cases, this is the address of the local host, except for multi-homed hosts (machines with more than one IP interface).
Setting this to 0 (default) enables the system to choose a port at random. The chosen port will be shown by LocalPort after the connection is established.
LocalPort cannot be changed once a connection is made. Any attempt to set this when a connection is active will generate an error.
This; setting is useful when trying to connect to services that require a trusted port in the client side. An example is the remote shell (rsh) service in UNIX systems.
If an EOL string is found in the input stream before MaxLineLength bytes are received, the DataIn event is fired with the EOL parameter set to True, and the buffer is reset.
If no EOL is found, and MaxLineLength bytes are accumulated in the buffer, the DataIn event is fired with the EOL parameter set to False, and the buffer is reset.
The minimum value for MaxLineLength is 256 bytes. The default value is 2048 bytes.
www.google.com;www.nsoftware.com
Note: This value is not applicable in Java.
By default, this config is set to false.
0 | IPv4 Only |
1 | IPv6 Only |
2 | IPv6 with IPv4 fallback |
SSL Config Settings
When enabled, SSL packet logs are output using the SSLStatus event, which will fire each time an SSL packet is sent or received.
Enabling this setting has no effect if SSLProvider is set to Platform.
The path set by this property should point to a directory containing CA certificates in PEM format. The files each contain one CA certificate. The files are looked up by the CA subject name hash value, which must hence be available. If more than one CA certificate with the same name hash value exist, the extension must be different (e.g. 9d66eef0.0, 9d66eef0.1 etc). OpenSSL recommends to use the c_rehash utility to create the necessary links. Please refer to the OpenSSL man page SSL_CTX_load_verify_locations(3) for details.
The file set by this property should contain a list of CA certificates in PEM format. The file can contain several CA certificates identified by
-----BEGIN CERTIFICATE-----
... (CA certificate in base64 encoding) ...
-----END CERTIFICATE-----
sequences. Before, between, and after the certificates text is allowed which can be used e.g. for descriptions of the certificates. Please refer to the OpenSSL man page SSL_CTX_load_verify_locations(3) for details.
The format of this string is described in the OpenSSL man page ciphers(1) section "CIPHER LIST FORMAT". Please refer to it for details. The default string "DEFAULT" is determined at compile time and is normally equivalent to "ALL:!ADH:RC4+RSA:+SSLv2:@STRENGTH".
By default OpenSSL uses the device file "/dev/urandom" to seed the PRNG and setting OpenSSLPrngSeedData is not required. If set, the string specified is used to seed the PRNG.
If set to true, the component will reuse the context if and only if the following criteria are met:
- The target host name is the same.
- The system cache entry has not expired (default timeout is 10 hours).
- The application process that calls the function is the same.
- The logon session is the same.
- The instance of the component is the same.
-----BEGIN CERTIFICATE----- MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw ... eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w F0I1XhM+pKj7FjDr+XNj -----END CERTIFICATE----- \r \n -----BEGIN CERTIFICATE----- MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp .. d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA -----END CERTIFICATE-----
When set to 0 (default) the CRL check will not be performed by the component. When set to 1, it will attempt to perform the CRL check, but will continue without an error if the server's certificate does not support CRL. When set to 2, it will perform the CRL check and will throw an error if CRL is not supported.
This configuration setting is only supported in the Java, C#, and C++ editions. In the C++ edition, it is only supported on Windows operating systems.
When set to 0 (default) the component will not perform an OCSP check. When set to 1, it will attempt to perform the OCSP check, but will continue without an error if the server's certificate does not support OCSP. When set to 2, it will perform the OCSP check and will throw an error if OCSP is not supported.
This configuration setting is only supported in the Java, C#, and C++ editions. In the C++ edition, it is only supported on Windows operating systems.
Please note that this setting contains the minimum cipher strength requested from the security library. The actual cipher strength used for the connection is shown by the SSLStatus event.
Use this setting with caution. Requesting a lower cipher strength than necessary could potentially cause serious security vulnerabilities in your application.
When the provider is OpenSSL, SSLCipherStrength is currently not supported. This functionality is instead made available through the OpenSSLCipherList config setting.
By default, the enabled cipher suites will include all available ciphers ("*").
The special value "*" means that the component will pick all of the supported cipher suites. If SSLEnabledCipherSuites is set to any other value, only the specified cipher suites will be considered.
Multiple cipher suites are separated by semicolons.
Example values when SSLProvider is set to Platform:
obj.config("SSLEnabledCipherSuites=*");
obj.config("SSLEnabledCipherSuites=CALG_AES_256");
obj.config("SSLEnabledCipherSuites=CALG_AES_256;CALG_3DES");
Possible values when SSLProvider is set to Platform include:
- CALG_3DES
- CALG_3DES_112
- CALG_AES
- CALG_AES_128
- CALG_AES_192
- CALG_AES_256
- CALG_AGREEDKEY_ANY
- CALG_CYLINK_MEK
- CALG_DES
- CALG_DESX
- CALG_DH_EPHEM
- CALG_DH_SF
- CALG_DSS_SIGN
- CALG_ECDH
- CALG_ECDH_EPHEM
- CALG_ECDSA
- CALG_ECMQV
- CALG_HASH_REPLACE_OWF
- CALG_HUGHES_MD5
- CALG_HMAC
- CALG_KEA_KEYX
- CALG_MAC
- CALG_MD2
- CALG_MD4
- CALG_MD5
- CALG_NO_SIGN
- CALG_OID_INFO_CNG_ONLY
- CALG_OID_INFO_PARAMETERS
- CALG_PCT1_MASTER
- CALG_RC2
- CALG_RC4
- CALG_RC5
- CALG_RSA_KEYX
- CALG_RSA_SIGN
- CALG_SCHANNEL_ENC_KEY
- CALG_SCHANNEL_MAC_KEY
- CALG_SCHANNEL_MASTER_HASH
- CALG_SEAL
- CALG_SHA
- CALG_SHA1
- CALG_SHA_256
- CALG_SHA_384
- CALG_SHA_512
- CALG_SKIPJACK
- CALG_SSL2_MASTER
- CALG_SSL3_MASTER
- CALG_SSL3_SHAMD5
- CALG_TEK
- CALG_TLS1_MASTER
- CALG_TLS1PRF
obj.config("SSLEnabledCipherSuites=*");
obj.config("SSLEnabledCipherSuites=TLS_DHE_DSS_WITH_AES_128_CBC_SHA");
obj.config("SSLEnabledCipherSuites=TLS_DHE_DSS_WITH_AES_128_CBC_SHA;TLS_DH_ANON_WITH_AES_128_CBC_SHA");
Possible values when SSLProvider is set to Internal include:
- TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
- TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
- TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
- TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
- TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384
- TLS_RSA_WITH_AES_256_GCM_SHA384
- TLS_RSA_WITH_AES_128_GCM_SHA256
- TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256
- TLS_DHE_DSS_WITH_AES_256_GCM_SHA384
- TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
- TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384
- TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256
- TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
- TLS_DHE_DSS_WITH_AES_128_GCM_SHA256
- TLS_DH_RSA_WITH_AES_128_GCM_SHA256 (Not Recommended)
- TLS_DH_RSA_WITH_AES_256_GCM_SHA384 (Not Recommended)
- TLS_DH_DSS_WITH_AES_128_GCM_SHA256 (Not Recommended)
- TLS_DH_DSS_WITH_AES_256_GCM_SHA384 (Not Recommended)
- TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
- TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
- TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
- TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
- TLS_RSA_WITH_AES_256_CBC_SHA256
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
- TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
- TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
- TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
- TLS_RSA_WITH_AES_128_CBC_SHA256
- TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256
- TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256
- TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
- TLS_RSA_WITH_AES_256_CBC_SHA
- TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
- TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
- TLS_DHE_RSA_WITH_AES_256_CBC_SHA
- TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
- TLS_DHE_DSS_WITH_AES_256_CBC_SHA
- TLS_RSA_WITH_AES_128_CBC_SHA
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
- TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
- TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA
- TLS_ECDH_RSA_WITH_AES_128_CBC_SHA
- TLS_DHE_RSA_WITH_AES_128_CBC_SHA
- TLS_DHE_DSS_WITH_AES_128_CBC_SHA
- TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA
- TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
- TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA
- TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA
- TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
- TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
- TLS_RSA_WITH_3DES_EDE_CBC_SHA
- TLS_RSA_WITH_DES_CBC_SHA
- TLS_DHE_RSA_WITH_DES_CBC_SHA
- TLS_DHE_DSS_WITH_DES_CBC_SHA
- TLS_RSA_WITH_RC4_128_MD5
- TLS_RSA_WITH_RC4_128_SHA
When TLS 1.3 is negotiated (see SSLEnabledProtocols) only the following cipher suites are supported:
- TLS_AES_256_GCM_SHA384
- TLS_CHACHA20_POLY1305_SHA256
- TLS_AES_128_GCM_SHA256
SSLEnabledCipherSuites is used together with SSLCipherStrength.
Not all supported protocols are enabled by default (the value of this setting is 4032). If you want more granular control over the enabled protocols, you can set this property to the binary 'OR' of one or more of the following values:
TLS1.3 | 12288 (Hex 3000) |
TLS1.2 | 3072 (Hex C00) (Default) |
TLS1.1 | 768 (Hex 300) (Default) |
TLS1 | 192 (Hex C0) (Default) |
SSL3 | 48 (Hex 30) [Platform Only] |
SSL2 | 12 (Hex 0C) [Platform Only] |
SSLEnabledProtocols - TLS 1.3 Notes
By default when TLS 1.3 is enabled the component will use the internal TLS implementation when the SSLProvider is set to Automatic for all editions.
In editions which are designed to run on Windows SSLProvider can be set to Platform to use the platform implementation instead of the internal implementation. When configured in this manner, please note that the platform provider is only supported on Windows 11 / Windows Server 2022 and up. The default internal provider is available on all platforms and is not restricted to any specific OS version.
If set to 1 (Platform provider) please be aware of the following notes:
- The platform provider is only available on Windows 11 / Windows Server 2022 and up.
- SSLEnabledCipherSuites and other similar SSL configuration settings are not supported.
- If SSLEnabledProtocols includes both TLS 1.3 and TLS 1.2 the above restrictions are still applicable even if TLS 1.2 is negotiated. Enabling TLS 1.3 with the platform provider changes the implementation used for all TLS versions.
SSLEnabledProtocols: SSL2 and SSL3 Notes:
SSL 2.0 and 3.0 are not supported by the component when the SSLProvider is set to internal. To use SSL 2.0 or SSL 3.0, the platform security API must have the protocols enabled and SSLProvider needs to be set to platform.
This setting is only applicable when SSLProvider is set to Internal.
If set to True all certificates returned by the server will be present in the Encoded parameter of the SSLServerAuthentication event. This includes the leaf certificate, any intermediate certificate, and the root certificate.
When set, the component will save the session secrets in the same format as the SSLKEYLOGFILE environment variable functionality used by most major browsers and tools such as Chrome, Firefox, and cURL. This file can then be used in tools such as Wireshark to decrypt TLS traffice for debugging purposes. When writing to this file the component will only append, it will not overwrite previous values.
Note: This setting is only applicable when SSLProvider is set to Internal.
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedCipher[connId]");
Note: For server components (e.g.TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedCipherStrength[connId]");
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedCipherSuite[connId]");
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedKeyExchange[connId]");
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedKeyExchangeStrength[connId]");
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedVersion[connId]");
0x00000001 | Ignore time validity status of certificate. |
0x00000002 | Ignore time validity status of CTL. |
0x00000004 | Ignore non-nested certificate times. |
0x00000010 | Allow unknown Certificate Authority. |
0x00000020 | Ignore wrong certificate usage. |
0x00000100 | Ignore unknown certificate revocation status. |
0x00000200 | Ignore unknown CTL signer revocation status. |
0x00000400 | Ignore unknown Certificate Authority revocation status. |
0x00000800 | Ignore unknown Root revocation status. |
0x00008000 | Allow test Root certificate. |
0x00004000 | Trust test Root certificate. |
0x80000000 | Ignore non-matching CN (certificate CN not-matching server name). |
This functionality is currently not available when the provider is OpenSSL.
The value of this setting is a newline (CrLf) separated list of certificates. For instance:
-----BEGIN CERTIFICATE----- MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw ... eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w F0I1XhM+pKj7FjDr+XNj -----END CERTIFICATE----- \r \n -----BEGIN CERTIFICATE----- MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp .. d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA -----END CERTIFICATE-----
When specified the component will verify that the server certificate signature algorithm is among the values specified in this setting. If the server certificate signature algorithm is unsupported the component raises an exception.
The format of this value is a comma separated list of hash-signature combinations. For instance:
component.SSLProvider = TCPClientSSLProviders.sslpInternal;
component.Config("SSLEnabledProtocols=3072"); //TLS 1.2
component.Config("TLS12SignatureAlgorithms=sha256-rsa,sha256-dsa,sha1-rsa,sha1-dsa");
The default value for this setting is sha512-ecdsa,sha512-rsa,sha512-dsa,sha384-ecdsa,sha384-rsa,sha384-dsa,sha256-ecdsa,sha256-rsa,sha256-dsa,sha224-ecdsa,sha224-rsa,sha224-dsa,sha1-ecdsa,sha1-rsa,sha1-dsa.
In order to not restrict the server's certificate signature algorithm, specify an empty string as the value for this setting, which will cause the signature_algorithms TLS 1.2 extension to not be sent.
The default value is ecdhe_secp256r1,ecdhe_secp384r1,ecdhe_secp521r1.
When using TLS 1.2 and SSLProvider is set to Internal, the values refer to the supported groups for ECC. The following values are supported:
- "ecdhe_secp256r1" (default)
- "ecdhe_secp384r1" (default)
- "ecdhe_secp521r1" (default)
The default value is set to balance common supported groups and the computational resources required to generate key shares. As a result only some groups are included by default in this setting.
Note: All supported groups can always be used during the handshake even if not listed here, but if a group is used which is not present in this list it will incur an additional round trip and time to generate the key share for that group.
In most cases this setting does not need to be modified. This should only be modified if there is a specific reason to do so.
The default value is ecdhe_x25519,ecdhe_secp256r1,ecdhe_secp384r1,ffdhe_2048,ffdhe_3072
The values are ordered from most preferred to least preferred. The following values are supported:
- "ecdhe_x25519" (default)
- "ecdhe_x448"
- "ecdhe_secp256r1" (default)
- "ecdhe_secp384r1" (default)
- "ecdhe_secp521r1"
- "ffdhe_2048" (default)
- "ffdhe_3072" (default)
- "ffdhe_4096"
- "ffdhe_6144"
- "ffdhe_8192"
- "ed25519" (default)
- "ed448" (default)
- "ecdsa_secp256r1_sha256" (default)
- "ecdsa_secp384r1_sha384" (default)
- "ecdsa_secp521r1_sha512" (default)
- "rsa_pkcs1_sha256" (default)
- "rsa_pkcs1_sha384" (default)
- "rsa_pkcs1_sha512" (default)
- "rsa_pss_sha256" (default)
- "rsa_pss_sha384" (default)
- "rsa_pss_sha512" (default)
The default value is ecdhe_x25519,ecdhe_x448,ecdhe_secp256r1,ecdhe_secp384r1,ecdhe_secp521r1,ffdhe_2048,ffdhe_3072,ffdhe_4096,ffdhe_6144,ffdhe_8192
The values are ordered from most preferred to least preferred. The following values are supported:
- "ecdhe_x25519" (default)
- "ecdhe_x448" (default)
- "ecdhe_secp256r1" (default)
- "ecdhe_secp384r1" (default)
- "ecdhe_secp521r1" (default)
- "ffdhe_2048" (default)
- "ffdhe_3072" (default)
- "ffdhe_4096" (default)
- "ffdhe_6144" (default)
- "ffdhe_8192" (default)
Socket Config Settings
Note: This option is not valid for UDP ports.
Some TCP/IP implementations do not support variable buffer sizes. If that is the case, when the component is activated the InBufferSize reverts to its defined size. The same happens if you attempt to make it too large or too small.
Some TCP/IP implementations do not support variable buffer sizes. If that is the case, when the component is activated the OutBufferSize reverts to its defined size. The same happens if you attempt to make it too large or too small.
Base Config Settings
The following is a list of valid code page identifiers:
Identifier | Name |
037 | IBM EBCDIC - U.S./Canada |
437 | OEM - United States |
500 | IBM EBCDIC - International |
708 | Arabic - ASMO 708 |
709 | Arabic - ASMO 449+, BCON V4 |
710 | Arabic - Transparent Arabic |
720 | Arabic - Transparent ASMO |
737 | OEM - Greek (formerly 437G) |
775 | OEM - Baltic |
850 | OEM - Multilingual Latin I |
852 | OEM - Latin II |
855 | OEM - Cyrillic (primarily Russian) |
857 | OEM - Turkish |
858 | OEM - Multilingual Latin I + Euro symbol |
860 | OEM - Portuguese |
861 | OEM - Icelandic |
862 | OEM - Hebrew |
863 | OEM - Canadian-French |
864 | OEM - Arabic |
865 | OEM - Nordic |
866 | OEM - Russian |
869 | OEM - Modern Greek |
870 | IBM EBCDIC - Multilingual/ROECE (Latin-2) |
874 | ANSI/OEM - Thai (same as 28605, ISO 8859-15) |
875 | IBM EBCDIC - Modern Greek |
932 | ANSI/OEM - Japanese, Shift-JIS |
936 | ANSI/OEM - Simplified Chinese (PRC, Singapore) |
949 | ANSI/OEM - Korean (Unified Hangul Code) |
950 | ANSI/OEM - Traditional Chinese (Taiwan; Hong Kong SAR, PRC) |
1026 | IBM EBCDIC - Turkish (Latin-5) |
1047 | IBM EBCDIC - Latin 1/Open System |
1140 | IBM EBCDIC - U.S./Canada (037 + Euro symbol) |
1141 | IBM EBCDIC - Germany (20273 + Euro symbol) |
1142 | IBM EBCDIC - Denmark/Norway (20277 + Euro symbol) |
1143 | IBM EBCDIC - Finland/Sweden (20278 + Euro symbol) |
1144 | IBM EBCDIC - Italy (20280 + Euro symbol) |
1145 | IBM EBCDIC - Latin America/Spain (20284 + Euro symbol) |
1146 | IBM EBCDIC - United Kingdom (20285 + Euro symbol) |
1147 | IBM EBCDIC - France (20297 + Euro symbol) |
1148 | IBM EBCDIC - International (500 + Euro symbol) |
1149 | IBM EBCDIC - Icelandic (20871 + Euro symbol) |
1200 | Unicode UCS-2 Little-Endian (BMP of ISO 10646) |
1201 | Unicode UCS-2 Big-Endian |
1250 | ANSI - Central European |
1251 | ANSI - Cyrillic |
1252 | ANSI - Latin I |
1253 | ANSI - Greek |
1254 | ANSI - Turkish |
1255 | ANSI - Hebrew |
1256 | ANSI - Arabic |
1257 | ANSI - Baltic |
1258 | ANSI/OEM - Vietnamese |
1361 | Korean (Johab) |
10000 | MAC - Roman |
10001 | MAC - Japanese |
10002 | MAC - Traditional Chinese (Big5) |
10003 | MAC - Korean |
10004 | MAC - Arabic |
10005 | MAC - Hebrew |
10006 | MAC - Greek I |
10007 | MAC - Cyrillic |
10008 | MAC - Simplified Chinese (GB 2312) |
10010 | MAC - Romania |
10017 | MAC - Ukraine |
10021 | MAC - Thai |
10029 | MAC - Latin II |
10079 | MAC - Icelandic |
10081 | MAC - Turkish |
10082 | MAC - Croatia |
12000 | Unicode UCS-4 Little-Endian |
12001 | Unicode UCS-4 Big-Endian |
20000 | CNS - Taiwan |
20001 | TCA - Taiwan |
20002 | Eten - Taiwan |
20003 | IBM5550 - Taiwan |
20004 | TeleText - Taiwan |
20005 | Wang - Taiwan |
20105 | IA5 IRV International Alphabet No. 5 (7-bit) |
20106 | IA5 German (7-bit) |
20107 | IA5 Swedish (7-bit) |
20108 | IA5 Norwegian (7-bit) |
20127 | US-ASCII (7-bit) |
20261 | T.61 |
20269 | ISO 6937 Non-Spacing Accent |
20273 | IBM EBCDIC - Germany |
20277 | IBM EBCDIC - Denmark/Norway |
20278 | IBM EBCDIC - Finland/Sweden |
20280 | IBM EBCDIC - Italy |
20284 | IBM EBCDIC - Latin America/Spain |
20285 | IBM EBCDIC - United Kingdom |
20290 | IBM EBCDIC - Japanese Katakana Extended |
20297 | IBM EBCDIC - France |
20420 | IBM EBCDIC - Arabic |
20423 | IBM EBCDIC - Greek |
20424 | IBM EBCDIC - Hebrew |
20833 | IBM EBCDIC - Korean Extended |
20838 | IBM EBCDIC - Thai |
20866 | Russian - KOI8-R |
20871 | IBM EBCDIC - Icelandic |
20880 | IBM EBCDIC - Cyrillic (Russian) |
20905 | IBM EBCDIC - Turkish |
20924 | IBM EBCDIC - Latin-1/Open System (1047 + Euro symbol) |
20932 | JIS X 0208-1990 & 0121-1990 |
20936 | Simplified Chinese (GB2312) |
21025 | IBM EBCDIC - Cyrillic (Serbian, Bulgarian) |
21027 | Extended Alpha Lowercase |
21866 | Ukrainian (KOI8-U) |
28591 | ISO 8859-1 Latin I |
28592 | ISO 8859-2 Central Europe |
28593 | ISO 8859-3 Latin 3 |
28594 | ISO 8859-4 Baltic |
28595 | ISO 8859-5 Cyrillic |
28596 | ISO 8859-6 Arabic |
28597 | ISO 8859-7 Greek |
28598 | ISO 8859-8 Hebrew |
28599 | ISO 8859-9 Latin 5 |
28605 | ISO 8859-15 Latin 9 |
29001 | Europa 3 |
38598 | ISO 8859-8 Hebrew |
50220 | ISO 2022 Japanese with no halfwidth Katakana |
50221 | ISO 2022 Japanese with halfwidth Katakana |
50222 | ISO 2022 Japanese JIS X 0201-1989 |
50225 | ISO 2022 Korean |
50227 | ISO 2022 Simplified Chinese |
50229 | ISO 2022 Traditional Chinese |
50930 | Japanese (Katakana) Extended |
50931 | US/Canada and Japanese |
50933 | Korean Extended and Korean |
50935 | Simplified Chinese Extended and Simplified Chinese |
50936 | Simplified Chinese |
50937 | US/Canada and Traditional Chinese |
50939 | Japanese (Latin) Extended and Japanese |
51932 | EUC - Japanese |
51936 | EUC - Simplified Chinese |
51949 | EUC - Korean |
51950 | EUC - Traditional Chinese |
52936 | HZ-GB2312 Simplified Chinese |
54936 | Windows XP: GB18030 Simplified Chinese (4 Byte) |
57002 | ISCII Devanagari |
57003 | ISCII Bengali |
57004 | ISCII Tamil |
57005 | ISCII Telugu |
57006 | ISCII Assamese |
57007 | ISCII Oriya |
57008 | ISCII Kannada |
57009 | ISCII Malayalam |
57010 | ISCII Gujarati |
57011 | ISCII Punjabi |
65000 | Unicode UTF-7 |
65001 | Unicode UTF-8 |
Identifier | Name |
1 | ASCII |
2 | NEXTSTEP |
3 | JapaneseEUC |
4 | UTF8 |
5 | ISOLatin1 |
6 | Symbol |
7 | NonLossyASCII |
8 | ShiftJIS |
9 | ISOLatin2 |
10 | Unicode |
11 | WindowsCP1251 |
12 | WindowsCP1252 |
13 | WindowsCP1253 |
14 | WindowsCP1254 |
15 | WindowsCP1250 |
21 | ISO2022JP |
30 | MacOSRoman |
10 | UTF16String |
0x90000100 | UTF16BigEndian |
0x94000100 | UTF16LittleEndian |
0x8c000100 | UTF32String |
0x98000100 | UTF32BigEndian |
0x9c000100 | UTF32LittleEndian |
65536 | Proprietary |
- Product: The product the license is for.
- Product Key: The key the license was generated from.
- License Source: Where the license was found (e.g., RuntimeLicense, License File).
- License Type: The type of license installed (e.g., Royalty Free, Single Server).
- Last Valid Build: The last valid build number for which the license will work.
This setting only works on these components: AS3Receiver, AS3Sender, Atom, Client(3DS), FTP, FTPServer, IMAP, OFTPClient, SSHClient, SCP, Server(3DS), Sexec, SFTP, SFTPServer, SSHServer, TCPClient, TCPServer.
Setting this configuration setting to true tells the component to use the internal implementation instead of using the system security libraries.
This setting is set to false by default on all platforms.
Trappable Errors (XMPP Component)
XMPP Errors
202 Invalid argument. | |
432 Array index out of bounds. | |
600 XMPP protocol error (server returned an error code; description follows). | |
601 Server disconnected. | |
602 Cannot change this property while connected. | |
603 Invalid XML received from server. | |
604 Invalid response received from server. | |
605 Server indicates TLS is required. | |
606 User requested SSL, but server does not support it. | |
607 Cannot authenticate. | |
620 Error hashing password. |
The component may also return one of the following error codes, which are inherited from other components.
TCPClient Errors
100 You cannot change the RemotePort at this time. A connection is in progress. | |
101 You cannot change the RemoteHost (Server) at this time. A connection is in progress. | |
102 The RemoteHost address is invalid (0.0.0.0). | |
104 Already connected. If you want to reconnect, close the current connection first. | |
106 You cannot change the LocalPort at this time. A connection is in progress. | |
107 You cannot change the LocalHost at this time. A connection is in progress. | |
112 You cannot change MaxLineLength at this time. A connection is in progress. | |
116 RemotePort cannot be zero. Please specify a valid service port number. | |
117 You cannot change the UseConnection option while the component is active. | |
135 Operation would block. | |
201 Timeout. | |
211 Action impossible in control's present state. | |
212 Action impossible while not connected. | |
213 Action impossible while listening. | |
301 Timeout. | |
302 Could not open file. | |
434 Unable to convert string to selected CodePage. | |
1105 Already connecting. If you want to reconnect, close the current connection first. | |
1117 You need to connect first. | |
1119 You cannot change the LocalHost at this time. A connection is in progress. | |
1120 Connection dropped by remote host. |
SSL Errors
270 Cannot load specified security library. | |
271 Cannot open certificate store. | |
272 Cannot find specified certificate. | |
273 Cannot acquire security credentials. | |
274 Cannot find certificate chain. | |
275 Cannot verify certificate chain. | |
276 Error during handshake. | |
280 Error verifying certificate. | |
281 Could not find client certificate. | |
282 Could not find server certificate. | |
283 Error encrypting data. | |
284 Error decrypting data. |
TCP/IP Errors
10004 [10004] Interrupted system call. | |
10009 [10009] Bad file number. | |
10013 [10013] Access denied. | |
10014 [10014] Bad address. | |
10022 [10022] Invalid argument. | |
10024 [10024] Too many open files. | |
10035 [10035] Operation would block. | |
10036 [10036] Operation now in progress. | |
10037 [10037] Operation already in progress. | |
10038 [10038] Socket operation on non-socket. | |
10039 [10039] Destination address required. | |
10040 [10040] Message too long. | |
10041 [10041] Protocol wrong type for socket. | |
10042 [10042] Bad protocol option. | |
10043 [10043] Protocol not supported. | |
10044 [10044] Socket type not supported. | |
10045 [10045] Operation not supported on socket. | |
10046 [10046] Protocol family not supported. | |
10047 [10047] Address family not supported by protocol family. | |
10048 [10048] Address already in use. | |
10049 [10049] Can't assign requested address. | |
10050 [10050] Network is down. | |
10051 [10051] Network is unreachable. | |
10052 [10052] Net dropped connection or reset. | |
10053 [10053] Software caused connection abort. | |
10054 [10054] Connection reset by peer. | |
10055 [10055] No buffer space available. | |
10056 [10056] Socket is already connected. | |
10057 [10057] Socket is not connected. | |
10058 [10058] Can't send after socket shutdown. | |
10059 [10059] Too many references, can't splice. | |
10060 [10060] Connection timed out. | |
10061 [10061] Connection refused. | |
10062 [10062] Too many levels of symbolic links. | |
10063 [10063] File name too long. | |
10064 [10064] Host is down. | |
10065 [10065] No route to host. | |
10066 [10066] Directory not empty | |
10067 [10067] Too many processes. | |
10068 [10068] Too many users. | |
10069 [10069] Disc Quota Exceeded. | |
10070 [10070] Stale NFS file handle. | |
10071 [10071] Too many levels of remote in path. | |
10091 [10091] Network subsystem is unavailable. | |
10092 [10092] WINSOCK DLL Version out of range. | |
10093 [10093] Winsock not loaded yet. | |
11001 [11001] Host not found. | |
11002 [11002] Non-authoritative 'Host not found' (try again or check DNS setup). | |
11003 [11003] Non-recoverable errors: FORMERR, REFUSED, NOTIMP. | |
11004 [11004] Valid name, no data record (check DNS setup). |