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

TipwXMPP

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.

Method List

The following is the full list of the methods of the component with short descriptions. Click on the links for further details.

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.

Config Settings

The following is a list of config settings for the component with short descriptions. Click on the links for further details.

AuthDomain Property (XMPP Component)

The domain under which the user will be authenticated.

Syntax

property AuthDomain: String read get_AuthDomain write set_AuthDomain;

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.

AuthMethods Property (XMPP Component)

Controls how the component authenticates itself with the XMPP server.

Syntax

property AuthMethods: String read get_AuthMethods write set_AuthMethods;

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

Buddies Property (XMPP Component)

Collection of buddies in the buddy list.

Syntax

property Buddies: TipwXMPPBuddyList read get_Buddies;

Remarks

After a Sync event is fired, this property will contain a collection of all buddies in the buddy list. The buddy list will be updated by the server when a successful call to RetrieveRoster has been made.

This property is read-only.

Connected Property (XMPP Component)

This indicates the component's login status.

Syntax

property Connected: Boolean read get_Connected write set_Connected;

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.

Firewall Property (XMPP Component)

A set of properties related to firewall access.

Syntax

property Firewall: TipwFirewall read get_Firewall write set_Firewall;

Remarks

This is a Firewall-type property, which contains fields describing the firewall through which the component will attempt to connect.

IMPort Property (XMPP Component)

The server port for XMPP (default 5222).

Syntax

property IMPort: Integer read get_IMPort write set_IMPort;

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.

IMServer Property (XMPP Component)

This is the instant messaging server.

Syntax

property IMServer: String read get_IMServer write set_IMServer;

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.

LocalDirectory Property (XMPP Component)

The directory to which received files are saved.

Syntax

property LocalDirectory: String read get_LocalDirectory write set_LocalDirectory;

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.

LocalFile Property (XMPP Component)

The path to the file that will be sent.

Syntax

property LocalFile: String read get_LocalFile write set_LocalFile;

Default Value

''

Remarks

This property specifies the local file that will be sent when calling SendFile. This property must be set before calling SendFile.

LocalHost Property (XMPP Component)

The name of the local host or user-assigned IP interface through which connections are initiated or accepted.

Syntax

property LocalHost: String read get_LocalHost write set_LocalHost;

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.

MessageHTML Property (XMPP Component)

This is the HTML version of the current message.

Syntax

property MessageHTML: String read get_MessageHTML write set_MessageHTML;

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.

MessageOtherData Property (XMPP Component)

This property contains extra data elements for the current message.

Syntax

property MessageOtherData: String read get_MessageOtherData write set_MessageOtherData;

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.

MessageSubject Property (XMPP Component)

This is the subject of the current message.

Syntax

property MessageSubject: String read get_MessageSubject write set_MessageSubject;

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.

MessageText Property (XMPP Component)

This is the plain text of the current message.

Syntax

property MessageText: String read get_MessageText write set_MessageText;

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.

MessageThread Property (XMPP Component)

This is the thread name of the current message.

Syntax

property MessageThread: String read get_MessageThread write set_MessageThread;

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.

MessageType Property (XMPP Component)

This is the type of the current message.

Syntax

property MessageType: TipwTJabberMessageTypes read get_MessageType write set_MessageType;

TipwTJabberMessageTypes = (
  jmtNormal,
  jmtChat,
  jmtGroupChat,
  jmtHeadline,
  jmtError
);

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:

This property is not available at design time.

Password Property (XMPP Component)

This is the user's password.

Syntax

property Password: String read get_Password write set_Password;

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.

Presence Property (XMPP Component)

This is the availability of the entity.

Syntax

property Presence: TipwTJabberPresenceCodes read get_Presence write set_Presence;

TipwTJabberPresenceCodes = (
  pcOffline,
  pcChat,
  pcAway,
  pcXA,
  pcDND
);

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:

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.

Resource Property (XMPP Component)

This is the resource for the current session.

Syntax

property Resource: String read get_Resource write set_Resource;

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.

ServerDomain Property (XMPP Component)

The XMPP server's domain.

Syntax

property ServerDomain: String read get_ServerDomain write set_ServerDomain;

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.

SSLAcceptServerCertEncoded Property (XMPP Component)

This is the certificate (PEM/Base64 encoded).

Syntax

property SSLAcceptServerCertEncoded: String read get_SSLAcceptServerCertEncoded write set_SSLAcceptServerCertEncoded;
property SSLAcceptServerCertEncodedB: TBytes read get_SSLAcceptServerCertEncodedB write set_SSLAcceptServerCertEncodedB;

Default Value

''

Remarks

This is the certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The Store and Subject properties also may be used to specify a certificate.

When Encoded is set, a search is initiated in the current Store for the private key of the certificate. If the key is found, Subject is updated to reflect the full subject of the selected certificate; otherwise, Subject is set to an empty string.

This property is not available at design time.

SSLCertEncoded Property (XMPP Component)

This is the certificate (PEM/Base64 encoded).

Syntax

property SSLCertEncoded: String read get_SSLCertEncoded write set_SSLCertEncoded;
property SSLCertEncodedB: TBytes read get_SSLCertEncodedB write set_SSLCertEncodedB;

Default Value

''

Remarks

This is the certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The Store and Subject properties also may be used to specify a certificate.

When Encoded is set, a search is initiated in the current Store for the private key of the certificate. If the key is found, Subject is updated to reflect the full subject of the selected certificate; otherwise, Subject is set to an empty string.

This property is not available at design time.

SSLCertStore Property (XMPP Component)

This is the name of the certificate store for the client certificate.

Syntax

property SSLCertStore: String read get_SSLCertStore write set_SSLCertStore;
property SSLCertStoreB: TBytes read get_SSLCertStoreB write set_SSLCertStoreB;

Default Value

'MY'

Remarks

This is the name of the certificate store for the client certificate.

The StoreType property denotes the type of the certificate store specified by Store. If the store is password protected, specify the password in StorePassword.

Store is used in conjunction with the Subject property to specify client certificates. If Store has a value, and Subject or Encoded is set, a search for a certificate is initiated. Please see the Subject property for details.

Designations of certificate stores are platform dependent.

The following designations are the most common User and Machine certificate stores in Windows:

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).

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 SSLCertStorePassword: String read get_SSLCertStorePassword write set_SSLCertStorePassword;

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.

SSLCertStoreType Property (XMPP Component)

This is the type of certificate store for this certificate.

Syntax

property SSLCertStoreType: TipwCertStoreTypes read get_SSLCertStoreType write set_SSLCertStoreType;

TipwCertStoreTypes = (
  cstUser,
  cstMachine,
  cstPFXFile,
  cstPFXBlob,
  cstJKSFile,
  cstJKSBlob,
  cstPEMKeyFile,
  cstPEMKeyBlob,
  cstPublicKeyFile,
  cstPublicKeyBlob,
  cstSSHPublicKeyBlob,
  cstP7BFile,
  cstP7BBlob,
  cstSSHPublicKeyFile,
  cstPPKFile,
  cstPPKBlob,
  cstXMLFile,
  cstXMLBlob,
  cstJWKFile,
  cstJWKBlob,
  cstSecurityKey,
  cstBCFKSFile,
  cstBCFKSBlob,
  cstPKCS11,
  cstAuto
);

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:

SSLCertSubject Property (XMPP Component)

This is the subject of the certificate used for client authentication.

Syntax

property SSLCertSubject: String read get_SSLCertSubject write set_SSLCertSubject;

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:

If a field value contains a comma, it must be quoted.

SSLEnabled Property (XMPP Component)

Whether TLS/SSL is enabled.

Syntax

property SSLEnabled: Boolean read get_SSLEnabled write set_SSLEnabled;

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.

SSLProvider Property (XMPP Component)

This specifies the SSL/TLS implementation to use.

Syntax

property SSLProvider: TipwTSSLProviders read get_SSLProvider write set_SSLProvider;

TipwTSSLProviders = (
  sslpAutomatic,
  sslpPlatform,
  sslpInternal
);

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:

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, on Windows the component will use the platform implementation. On Linux/macOS the component will use the internal implementation. When TLS 1.3 is enabled via SSLEnabledProtocols the internal implementation is used on all platforms.

SSLServerCertEncoded Property (XMPP Component)

This is the certificate (PEM/Base64 encoded).

Syntax

property SSLServerCertEncoded: String read get_SSLServerCertEncoded;
property SSLServerCertEncodedB: TBytes read get_SSLServerCertEncodedB;

Default Value

''

Remarks

This is the certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The Store and Subject properties also may be used to specify a certificate.

When Encoded is set, a search is initiated in the current Store for the private key of the certificate. If the key is found, Subject is updated to reflect the full subject of the selected certificate; otherwise, Subject is set to an empty string.

This property is read-only and not available at design time.

SSLStartMode Property (XMPP Component)

Determines how the component starts the SSL negotiation.

Syntax

property SSLStartMode: TipwTSSLStartModes read get_SSLStartMode write set_SSLStartMode;

TipwTSSLStartModes = (
  sslAutomatic,
  sslImplicit,
  sslExplicit,
  sslNone
);

Default Value

sslNone

Remarks

The SSLStartMode property may have one of the following values:

Status Property (XMPP Component)

Description of the availability of this entity.

Syntax

property Status: String read get_Status write set_Status;

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:

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.

Timeout Property (XMPP Component)

A timeout for the component.

Syntax

property Timeout: Integer read get_Timeout write set_Timeout;

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.

User Property (XMPP Component)

The user portion of this entity's Jabber ID.

Syntax

property User: String read get_User write set_User;

Default Value

''

Remarks

The User property is a unique username associated with this entity and set at time of registration under the field 'user'.

UserDomain Property (XMPP Component)

Gets or sets the domain value used for Jabber IDs.

Syntax

property UserDomain: String read get_UserDomain write set_UserDomain;

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.

UserInfo Property (XMPP Component)

Collection of named registration fields.

Syntax

property UserInfo: TipwXMPPUserInfoList read get_UserInfo write set_UserInfo;

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:

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.

This collection is a hashtable type of collection where the field string is used as the key to the desired XMPP user info object.

Example (Setting New User Information)

xmpp1.QueryRegister("server"); xmpp1.UserInfoCount = 2 xmpp1.UserInfoField(0) = "Username" xmpp1.UserInfoValue(0) = "newuser" xmpp1.UserInfoField(1) = "Password" xmpp1.UserInfoValue(1) = "newpass" xmpp1.Register("server");

This property is not available at design time.

Add Method (XMPP Component)

This method will add an entity to this entity's roster.

Syntax

procedure Add(JabberId: String; Name: String; Groups: String);

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

procedure Cancel(JabberId: String);

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

procedure ChangePassword(Password: String);

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

procedure ChangePresence(PresenceCode: Integer; Status: String);

Remarks

PresenceCode should correspond the possible values of the Presence property:

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

function Config(ConfigurationString: String): String;

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

procedure 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

procedure ConnectTo(User: String; Password: String);

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

procedure 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

procedure 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

procedure 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

procedure ProbePresence(JabberId: String);

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

procedure QueryRegister(XMPPServer: String);

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:

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

procedure Register(XMPPServer: String);

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:

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

procedure Remove(JabberId: String; Name: String; Group: String);

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

procedure 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

procedure 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

procedure SendCommand(Command: String);

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

procedure SendFile(JabberId: String);

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.

SendMessage Method (XMPP Component)

This method will send a message to the specified user.

Syntax

function SendMessage(JabberId: String): String;

Remarks

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 associates several properties with messages it receives and sends. When it receives a message, the component will parse out the corresponding values and set these properties before firing a MessageIn event. After the event returns control to the component, the properties will be cleared (ie, they will be set to the empty string, '').

Before sending a message, the application should set the appropriate properties to be associated with the message. The component will send only properties with non-empty string values (''), and will clear all properties after a successful send.

The associated properties are the following:

If the parameter passed to SendMessage is prefixed with "@" the component will interpret the value as a domain when constructing the message. This allows for sending directly to sub-domains.

Note: the XMPP component will generate and return a unique identifier for each message sent. This identifier can be used to track messages in conjunction with various Jabber Extension Protocols.

SetUserInfoField Method (XMPP Component)

This method will add a user information field for registration.

Syntax

procedure SetUserInfoField(Field: String; Value: String);

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:

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

procedure SubscribeTo(JabberId: String);

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

procedure 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

procedure UnsubscribeTo(JabberId: String);

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

procedure UpdateBuddyGroup(BuddyIndex: Integer; Group: String);

Remarks

This method updates the associated groups for the buddy specified by BuddyIndex.

After the Sync event has fired the Group 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

type TBuddyUpdateEvent = procedure (
  Sender: TObject;
  BuddyIdx: Integer
) of Object;

property OnBuddyUpdate: TBuddyUpdateEvent 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

type TConnectedEvent = procedure (
  Sender: TObject;
  StatusCode: Integer;
  const Description: String
) of Object;

property OnConnected: TConnectedEvent 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

type TConnectionStatusEvent = procedure (
  Sender: TObject;
  const ConnectionEvent: String;
  StatusCode: Integer;
  const Description: String
) of Object;

property OnConnectionStatus: TConnectionStatusEvent 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:

Disconnected Event (XMPP Component)

This event is fired when the chat service connection is lost.

Syntax

type TDisconnectedEvent = procedure (
  Sender: TObject;
  StatusCode: Integer;
  const Description: String
) of Object;

property OnDisconnected: TDisconnectedEvent 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

type TEndTransferEvent = procedure (
  Sender: TObject;
  Direction: Integer;
  const FileId: String;
  const Filename: String;
  Success: Boolean
) of Object;

property OnEndTransfer: TEndTransferEvent 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

type TErrorEvent = procedure (
  Sender: TObject;
  ErrorCode: Integer;
  const Description: String
) of Object;

property OnError: TErrorEvent 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

type TIQEvent = procedure (
  Sender: TObject;
  const Iq: String;
  const Id: String;
  const From: String;
  const IqType: String;
  var Ignore: Boolean
) of Object;

property OnIQ: TIQEvent 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:

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

type TMessageInEvent = procedure (
  Sender: TObject;
  const MessageId: String;
  const From: String;
  const Domain: String;
  const Resource: String;
  MessageType: Integer;
  const Subject: String;
  const MessageThread: String;
  const MessageText: String;
  const MessageHTML: String;
  const Other: String
) of Object;

property OnMessageIn: TMessageInEvent 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

type TPITrailEvent = procedure (
  Sender: TObject;
  Direction: Integer;
  const Pi: String
) of Object;

property OnPITrail: TPITrailEvent 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:

The Pi parameter contains the PI message.

Presence Event (XMPP Component)

This event is fired when the presence of a subscribed entity changes.

Syntax

type TPresenceEvent = procedure (
  Sender: TObject;
  const User: String;
  const Domain: String;
  const Resource: String;
  Availability: Integer;
  const Status: String
) of Object;

property OnPresence: TPresenceEvent 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:

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

type TReadyToSendEvent = procedure (
  Sender: TObject
) of Object;

property OnReadyToSend: TReadyToSendEvent 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

type TSSLServerAuthenticationEvent = procedure (
  Sender: TObject;
  CertEncoded: String;
  CertEncodedB: TBytes;
  const CertSubject: String;
  const CertIssuer: String;
  const Status: String;
  var Accept: Boolean
) of Object;

property OnSSLServerAuthentication: TSSLServerAuthenticationEvent 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)

Fired when secure connection progress messages are available.

Syntax

type TSSLStatusEvent = procedure (
  Sender: TObject;
  const Message: String
) of Object;

property OnSSLStatus: TSSLStatusEvent 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

type TStartTransferEvent = procedure (
  Sender: TObject;
  Direction: Integer;
  const FileId: String;
  const User: String;
  const Domain: String;
  const Resource: String;
  var Filename: String;
  const Datetime: String;
  Size: Int64;
  var Accept: Boolean
) of Object;

property OnStartTransfer: TStartTransferEvent 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

type TSubscriptionRequestEvent = procedure (
  Sender: TObject;
  const From: String;
  const Domain: String;
  var Accept: Boolean
) of Object;

property OnSubscriptionRequest: TSubscriptionRequestEvent 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

type TSyncEvent = procedure (
  Sender: TObject
) of Object;

property OnSync: TSyncEvent 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:

Please refer to Buddies properties property for more information.

Transfer Event (XMPP Component)

Fired during file transfer.

Syntax

type TTransferEvent = procedure (
  Sender: TObject;
  Direction: Integer;
  const FileId: String;
  const Filename: String;
  BytesTransferred: Int64;
  PercentDone: Integer;
  Text: String;
  TextB: TBytes;
  var Cancel: Boolean
) of Object;

property OnTransfer: TTransferEvent 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.

Firewall Type

The firewall the component will connect through.

Remarks

When connecting through a firewall, this type is used to specify different properties of the firewall, such as the firewall Host and the FirewallType.

Fields

Constructors

constructor Create();

XMPPBuddy Type

A buddy in the XMPP buddy list.

Remarks

This type describes a buddy in the user's buddy list. Each buddy in the list has certain properties associated with it, such as names, id, etc.

Fields

Constructors

constructor Create();

XMPPUserInfo Type

A named registration field.

Remarks

This type describes the user information that must be sent to the server during registration.

Fields

Constructors

constructor Create();

constructor Create(valField: String; valValue: String);

Config Settings (XMPP Component)

XMPP Config Settings

TCPClient Config Settings

SSL Config Settings

-----BEGIN CERTIFICATE-----
MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw
...
eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w
F0I1XhM+pKj7FjDr+XNj
-----END CERTIFICATE-----
\r \n
-----BEGIN CERTIFICATE-----
MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp
..
d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA
-----END CERTIFICATE-----

-----BEGIN CERTIFICATE-----
MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw
...
eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w
F0I1XhM+pKj7FjDr+XNj
-----END CERTIFICATE-----
\r \n
-----BEGIN CERTIFICATE-----
MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp
..
d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA
-----END CERTIFICATE-----

Socket Config Settings

Base Config Settings

Trappable Errors (XMPP Component)

XMPP Errors

The component may also return one of the following error codes, which are inherited from other components.

TCPClient Errors

SSL Errors

TCP/IP Errors