/mcpA XMPP connection status of "unloading" indicates that an action in the browser (such as refreshing the browser or clicking the back button) caused the XMPP connection to initiate the unloading process. Note The resourceID parameter is a unique identifier for the XMPP connection. Although the resourceID parameter is provided with every connection status change, the ID is not available until after a XMPP connection has been successfully established. It is possible that the XMPP connection reconnects with a different resourceID. A situation can occur where a gadget is loaded after the Finesse Desktop or gadget has already published connection information. In this case, have the gadget publish a request to a Finesse request topic, which forces the Finesse Desktop to publish the connection information again. For more information, see Finesse Requests. Finesse Notifications finesse.api.[resourceObject].[resourceID] Topic Name Gadgets subscribe to this topic. Topic Type If a user has any subscriptions for a particular notification, either created by the Finesse Desktop or by an explicit subscribe request (see Subscription Management on the Finesse Desktop), the Cisco Finesse Notification Service delivers updates through the established XMPP connection. The Finesse Desktop automatically handles the management of the XMPP event connection to the Notification Service. Any notifications that are delivered through the connection are converted to JavaScript Object, and then published by the Finesse Desktop to an OpenAjax Hub topic. The name of the topic matches the node on the Finesse Notification Service on which the notification was published. However, to comply with OpenAjax topic conventions, all slashes (/) are replaced with dots (.) and the leading slash is removed. To receive notifications, the gadgets must 1. Subscribe to the OpenAjax topic for a particular notification feed. This action ensures that no notifications are missed after sending the subscription request to Finesse Web Services. 2. If required, make a request to the Cisco Finesse Notification Service to create a subscription for the notification feed (see Subscription Management on the Finesse Desktop). When connecting to the Cisco Finesse Notification Service, you must always specify a resource to identify your connection. Issues occur if the resource is omitted when the connection is created. The resource “desktop” is reserved for the Finesse Desktop. Do not use this resource for other connections as it causes a conflict with the Finesse Desktop. In Finesse, each notification type has an equivalent topic to which gadgets can subscribe. For a list of available Finesse notifications, see Cisco Finesse Notifications and look under the "node" property. These notifications are structured as follows: { content : Raw object payload as a String, object : JavaScript object representation of the payload } Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 397 Finesse Desktop Gadget Development Finesse Notifications