Abstract: A cloud service stores and aggregates content that is obtained from different content sources using different protocols. For example, the content may include electronic messages, calendar information, contacts, social network content, feed data, search results, and the like. The cloud service aggregates content for each user based on the user's configuration settings. The cloud service may perform processing on the aggregated content before it is delivered and displayed to the user on the client device. For example, one or more views may be generated and stored by the cloud service before the view is requested from the client. Changes made to the aggregated content on the client may be synchronized with the content source. Searches may be made across all or a portion of the different content sources that are aggregated for a user.

Abstract: An e-mail system is running with a first synchronization mechanism synchronizing first application data between a service and a client computing system. A second synchronization mechanism synchronizes second application data between the service and the client computing system, using a second protocol. When a given proportion of the application data has been synchronized by the second synchronization mechanism, the application is controlled to use the second application data synchronized according to the second protocol.

Abstract: A cloud service stores and aggregates content that is obtained from different content sources using different protocols. For example, the content may include electronic messages, calendar information, contacts, social network content, feed data, search results, and the like. The cloud service aggregates content for each user based on the user's configuration settings. The cloud service may perform processing on the aggregated content before it is delivered and displayed to the user on the client device. For example, one or more views may be generated and stored by the cloud service before the view is requested from the client. Changes made to the aggregated content on the client may be synchronized with the content source. Searches may be made across all or a portion of the different content sources that are aggregated for a user.

Abstract: An e-mail system is running with a first synchronization mechanism synchronizing first application data between a service and a client computing system. A second synchronization mechanism synchronizes second application data between the service and the client computing system, using a second protocol. When a given proportion of the application data has been synchronized by the second synchronization mechanism, the application is controlled to use the second application data synchronized according to the second protocol.

Abstract: A call to view application data is received at a hosted service. A truncated form of non-synchronized relevant data is generated and an on-line view of the truncated form is generated. When the call is detected, a synchronization system also begins synchronizing data and a synchronized view is generated with the synchronized data. The on-line view is surfaced until the synchronized view is ready for surfacing, at which point the synchronized view replaces the on-line view.

Abstract: A cloud service stores and aggregates content that is obtained from different content sources using different protocols. For example, the content may include electronic messages, calendar information, contacts, social network content, feed data, search results, and the like. The cloud service aggregates content for each user based on the user's configuration settings. The cloud service may perform processing on the aggregated content before it is delivered and displayed to the user on the client device. For example, one or more views may be generated and stored by the cloud service before the view is requested from the client. Changes made to the aggregated content on the client may be synchronized with the content source. Searches may be made across all or a portion of the different content sources that are aggregated for a user.

Abstract: A cloud service stores and aggregates content that is obtained from different content sources using different protocols. For example, the content may include electronic messages, calendar information, contacts, social network content, feed data, search results, and the like. The cloud service aggregates content for each user based on the user's configuration settings. The cloud service may perform processing on the aggregated content before it is delivered and displayed to the user on the client device. For example, one or more views may be generated and stored by the cloud service before the view is requested from the client. Changes made to the aggregated content on the client may be synchronized with the content source. Searches may be made across all or a portion of the different content sources that are aggregated for a user.

Abstract: A cloud service stores and aggregates content that is obtained from different content sources using different protocols. For example, the content may include electronic messages, calendar information, contacts, social network content, feed data, search results, and the like. The cloud service aggregates content for each user based on the user's configuration settings. The cloud service may perform processing on the aggregated content before it is delivered and displayed to the user on the client device. For example, one or more views may be generated and stored by the cloud service before the view is requested from the client. Changes made to the aggregated content on the client may be synchronized with the content source. Searches may be made across all or a portion of the different content sources that are aggregated for a user.

Abstract: Systems, methods, and software are described herein to facilitate the enhanced updating of user interfaces to a service. In an implementation, an application renders a user interface to a service and an initial visualization is surfaced in response to the occurrence of an event. After surfacing the initial visualization, the application receives an update from the service that includes a proposed visualization and determines whether or not the proposed visualization accounts for the event. If the proposed visualization accounts for the event, the proposed visualization is surfaced in place of the initial visualization. But if the proposed visualization does not account for the event, the initial visualization may be persisted until another visualization is identified that accounts for the event.

Abstract: A cloud service stores and aggregates content that is obtained from different content sources using different protocols. For example, the content may include electronic messages, calendar information, contacts, social network content, feed data, search results, and the like. The cloud service aggregates content for each user based on the user's configuration settings. The cloud service may perform processing on the aggregated content before it is delivered and displayed to the user on the client device. For example, one or more views may be generated and stored by the cloud service before the view is requested from the client. Changes made to the aggregated content on the client may be synchronized with the content source. Searches may be made across all or a portion of the different content sources that are aggregated for a user.

Abstract: Real time collaboration is enabled by providing a notification to users attempting access to an item, such as a document or a resource, that another user has currently access to the item. The users may be notified automatically when the other user is done accessing the item or periodically as the item is being accessed by the other user. The notification(s) may also include a summary or complete list of changes such that any user accessing the item after the other user has the latest version.

Abstract: Online application state information is automatically saved for a user interacting with the application content. Saved states are presented to the user upon the user's return to the application. Upon the user's selection of a state, the user is presented with the online application populated with state information from prior interaction.

Abstract: Online application state information is automatically saved for a user interacting with the application content. Saved states are presented to the user upon the user's return to the application. Upon the user's selection of a state, the user is presented with the online application populated with state information from prior interaction.

Abstract: Real time collaboration is enabled by providing a notification to users attempting access to an item, such as a document or a resource, that another user has currently access to the item. The users may be notified automatically when the other user is done accessing the item or periodically as the item is being accessed by the other user. The notification(s) may also include a summary or complete list of changes such that any user accessing the item after the other user has the latest version.

Abstract: An XML digital signature standard is applied to an XML document to sign it. The XML digital signature is an XML fragment with a specified schema that includes (a) data to describe how the signature should be calculated (e.g., digest methods, filters, and data sources) and (b) actual signature data (e.g., digests and signature values). The data describing how the signature should be calculated (i.e., the “group (a)” data) is placed inside an XML digital signature template, which is then used (e.g., by an API (application programming interface)) to create the actual digital signature containing the “group (b)” data.

Abstract: An XML digital signature standard is applied to an XML document to sign it. The XML digital signature is an XML fragment with a specified schema that includes (a) data to describe how the signature should be calculated (e.g., digest methods, filters, and data sources) and (b) actual signature data (e.g., digests and signature values). The data describing how the signature should be calculated (i.e., the “group (a)” data) is placed inside an XML digital signature template, which is then used (e.g., by an API (application programming interface)) to create the actual digital signature containing the “group (b)” data.

Abstract: An enterprise software gateway, or interface, operable to remotely facilitate, by transparently performing protocol conversion and managing communication, access to a host system (22), such as a mainframe legacy system, by a client application or device (24), including software applications and input/output (I/O) devices. A viewer (28) is provided to allow for remote monitoring of interactions, including communication, between the host (22) and client (24), and to allow for remote configuration and control of the software gateway, thereby facilitating problem diagnosis and solution.