Abstract: A communication system has a plurality of collections. Each collection comprises a security boundary within which private data is accessible. Each collection is associated with a director. The directors receive messages that specify domains. When a director for a given collection receives a message, the director identifies one of the collections as being a home collection for the domain specified by the message. If the specified domain's home collection is the given collection or another collection within a given privacy boundary, the director forwards the message to a server pool associated with the specified domain's home collection. Otherwise, if the specified domain's home collection is not within the given privacy boundary, the director forwards the message to the director of the specified domain's home collection.

Abstract: Metadata is used to create customized user interface (UI) portions for an application. The metadata may be XML-based and can be interpreted and then rendered to implement a customized UI that also supports data binding between data and the UI controls. Once created, the metadata is processed by a rendering engine to display the UI controls. An interpreter may be used to interpret the metadata file before it is sent to the rendering engine. Neither the rendering engine nor the interpreter needs knowledge of the host application and provides support for arbitrary metadata driven UI. The metadata schema may include mechanisms to create custom controls for the UI; programmatically modify the UI controls by providing access to a code-behind assembly as well as support event handling for the UI controls.

Abstract: Architecture for a communications system enabling a user to provision a telephone at a new location without network administrative pre-configuring. An input component (e.g., keypad) receives a numeric extension and PIN. The extension is a telephone extension of the user and the PIN can be administratively assigned. A location component provides location information of an enterprise communications server to the telephone based on the extension. The telephone uses the location information to send messages to the enterprise communications server. A registration component registers the telephone with the enterprise communications server based on the numeric extension. A telephony address is returned to the telephone. An authentication component authenticates the telephone based on the PIN. Upon authentication, the extension is assigned to the telephone, and telephone communications can be sent and received from that location.

Abstract: Secure sharing of bound information is enabled in client applications associated with a backend LOB service. Bound item IDs are assigned to newly created bound items by a client, the items synchronized with the LOB system, a correlation ID received in response to the synchronization, and the two IDs mapped. A reverse sequence of actions is performed when the LOB service creates the bound item. In response to an attempt by a client to exchange bound information, the item is placed in a pending state and allowed to be received by a receiver upon successful completion of data transfer and LOB system permission of the exchange passing the bound item ID and the correlation ID. If the LOB system rejects the exchange, the item is placed in an unbound state and the receiver not allowed to receive the bound information.

Abstract: Secure sharing of bound information is enabled in client applications associated with a backend LOB service. Bound item IDs are assigned to newly created bound items by a client, the items synchronized with the LOB system, a correlation ID received in response to the synchronization, and the two IDs mapped. A reverse sequence of actions is performed when the LOB service creates the bound item. In response to an attempt by a client to exchange bound information, the item is placed in a pending state and allowed to be received by a receiver upon successful completion of data transfer and LOB system permission of the exchange passing the bound item ID and the correlation ID. If the LOB system rejects the exchange, the item is placed in an unbound state and the receiver not allowed to receive the bound information.

Abstract: Metadata is used to create customized user interface (UI) portions for an application. The metadata may be XML-based and can be interpreted and then rendered to implement a customized UI that also supports data binding between data and the UI controls. Once created, the metadata is processed by a rendering engine to display the UI controls. An interpreter may be used to interpret the metadata file before it sent to the rendering engine. Neither the rendering engine nor the interpreter needs knowledge of the host application and provides support for arbitrary metadata driven UI. The metadata schema may include mechanisms to create custom controls for the UI; programmatically modify the UI controls by providing access to a code-behind assembly as well as support event handling for the UI controls.