Abstract: Disclosed are embodiments that communicate label information for documents between two enterprise computer systems. The two computer systems operate asynchronous from each other, and have limited available resources for use in buffering information passing between them. To that end, traditional API architectures that utilize method calls and return parameters do not operate well in this environment, as a first computer systems resources can become exhausted if a second computer system is able to generate data faster than the first computer system can consume it. The problem is exacerbated if an error is experienced when processing the consumed data, especially if there are no resources available to store the data until the error can be cleared. To solve this problem, the disclosed embodiments provide an ability for a consumer to request that data previously delivered to it be delivered again by the producer, in some embodiments, after a specified time delay.

Abstract: Disclosed herein is a system for enabling a default label to be configured for a network location created to store files. The default label can be assigned at a time when the files are uploaded to the network location. An owner of the network location can define the default label to be assigned to the files. Whenever an unlabeled file is uploaded to the network location, the unlabeled file automatically inherits the default label. Furthermore, the system is configured to consider an order of label priority when determining whether to assign a default label to a previously labeled file to be uploaded to the network location. The system is configured to upgrade a file with a preassigned label of lower priority to the default label, while permitting another file to be stored without a label change if the preassigned label is of higher priority compared to the default label.

Abstract: Disclosed are embodiments that communicate label information for documents between two enterprise computer systems. The two computer systems operate asynchronous from each other, and have limited available resources for use in buffering information passing between them. To that end, traditional API architectures that utilize method calls and return parameters do not operate well in this environment, as a first computer systems resources can become exhausted if a second computer system is able to generate data faster than the first computer system can consume it. The problem is exacerbated if an error is experienced when processing the consumed data, especially if there are no resources available to store the data until the error can be cleared. To solve this problem, the disclosed embodiments provide an ability for a consumer to request that data previously delivered to it be delivered again by the producer, in some embodiments, after a specified time delay.

Abstract: The techniques disclosed herein enable systems to manage remote file storage systems while bolstering information security through file encryption on download and permissions labels. To achieve this, a site owner configures permissions for a network site that stores files and that enables encryption on download. Various users with file access via the permissions may then interact with the site. When a user downloads a file from the site, they receive an encrypted copy that includes a permissions label that synchronizes with the network site permissions. When a user attempts to interact with an encrypted file the permissions label is used by the system to determine whether the user is authorized to access the file. In addition, permissions that are changed at the network site can be propagated to downloaded encrypted copies. In this way, permissions can be enforced for all site files even when copies leave the network site.

Abstract: Disclosed herein is a system for enabling a default label to be configured for a network location created to store files. The default label can be assigned at a time when the files are uploaded to the network location. An owner of the network location can define the default label to be assigned to the files. Whenever an unlabeled file is uploaded to the network location, the unlabeled file automatically inherits the default label. Furthermore, the system is configured to consider an order of label priority when determining whether to assign a default label to a previously labeled file to be uploaded to the network location. The system is configured to upgrade a file with a preassigned label of lower priority to the default label, while permitting another file to be stored without a label change if the preassigned label is of higher priority compared to the default label.

Abstract: Disclosed are embodiments that communicate label information for documents between two enterprise computer systems. The two computer systems operate asynchronous from each other, and have limited available resources for use in buffering information passing between them. To that end, traditional API architectures that utilize method calls and return parameters do not operate well in this environment, as a first computer systems resources can become exhausted if a second computer system is able to generate data faster than the first computer system can consume it. The problem is exacerbated if an error is experienced when processing the consumed data, especially if there are no resources available to store the data until the error can be cleared. To solve this problem, the disclosed embodiments provide an ability for a consumer to request that data previously delivered to it be delivered again by the producer, in some embodiments, after a specified time delay.

Abstract: Techniques to manage remote events are described. An apparatus may comprise a processor circuit and a remote event application arranged for execution by the processor circuit. The remote event application may be operative to manage remote event notifications for a publisher entity and a subscriber entity. The remote event application may comprise, among other elements, an event monitor component operative to receive an external event notification message with a publisher entity event for the publisher entity. The event monitor component may select a custom event receiver component associated with the publisher entity from among multiple custom event receiver components, and send the external event notification message to the selected custom event receiver component. The custom event receiver component may implement custom business logic, such as code callouts designed for specific application programs or system programs. Other embodiments are described and claimed.

Abstract: Techniques to manage remote events are described. An apparatus may comprise a processor circuit and a remote event application arranged for execution by the processor circuit. The remote event application may be operative to manage remote event notifications for a publisher entity and a subscriber entity. The remote event application may comprise, among other elements, an event monitor component operative to receive an external event notification message with a publisher entity event for the publisher entity. The event monitor component may select a custom event receiver component associated with the publisher entity from among multiple custom event receiver components, and send the external event notification message to the selected custom event receiver component. The custom event receiver component may implement custom business logic, such as code callouts designed for specific application programs or system programs. Other embodiments are described and claimed.

Abstract: Techniques to manage remote events are described. An apparatus may comprise a processor circuit and a remote event application arranged for execution by the processor circuit. The remote event application may be operative to manage remote event notifications for a publisher entity and a subscriber entity. The remote event application may comprise, among other elements, an event monitor component operative to receive an external event notification message with a publisher entity event for the publisher entity. The event monitor component may select a custom event receiver component associated with the publisher entity from among multiple custom event receiver components, and send the external event notification message to the selected custom event receiver component. The custom event receiver component may implement custom business logic, such as code callouts designed for specific application programs or system programs. Other embodiments are described and claimed.

Abstract: Techniques to manage remote events are described. An apparatus may comprise a processor circuit and a remote event application arranged for execution by the processor circuit. The remote event application may be operative to manage remote event notifications for a publisher entity and a subscriber entity. The remote event application may comprise, among other elements, an event monitor component operative to receive an external event notification message with a publisher entity event for the publisher entity. The event monitor component may select a custom event receiver component associated with the publisher entity from among multiple custom event receiver components, and send the external event notification message to the selected custom event receiver component. The custom event receiver component may implement custom business logic, such as code callouts designed for specific application programs or system programs. Other embodiments are described and claimed.

Abstract: Techniques to manage remote events are described. An apparatus may comprise a processor circuit and a remote event application arranged for execution by the processor circuit. The remote event application may be operative to manage remote event notifications for a publisher entity and a subscriber entity. The remote event application may comprise, among other elements, an event monitor component operative to receive an external event notification message with a publisher entity event for the publisher entity. The event monitor component may select a custom event receiver component associated with the publisher entity from among multiple custom event receiver components, and send the external event notification message to the selected custom event receiver component. The custom event receiver component may implement custom business logic, such as code callouts designed for specific application programs or system programs. Other embodiments are described and claimed.

Abstract: Techniques to manage remote events are described. An apparatus may comprise a processor circuit and a remote event application arranged for execution by the processor circuit. The remote event application may be operative to manage remote event notifications for a publisher entity and a subscriber entity. The remote event application may comprise, among other elements, an event monitor component operative to receive an external event notification message with a publisher entity event for the publisher entity. The event monitor component may select a custom event receiver component associated with the publisher entity from among multiple custom event receiver components, and send the external event notification message to the selected custom event receiver component. The custom event receiver component may implement custom business logic, such as code callouts designed for specific application programs or system programs. Other embodiments are described and claimed.

Abstract: Techniques to manage remote events are described. An apparatus may comprise a processor circuit and a remote event application arranged for execution by the processor circuit. The remote event application may be operative to manage remote event notifications for a publisher entity and a subscriber entity. The remote event application may comprise, among other elements, an event monitor component operative to receive an external event notification message with a publisher entity event for the publisher entity. The event monitor component may select a custom event receiver component associated with the publisher entity from among multiple custom event receiver components, and send the external event notification message to the selected custom event receiver component. The custom event receiver component may implement custom business logic, such as code callouts designed for specific application programs or system programs. Other embodiments are described and claimed.

Abstract: Techniques to selectively access meeting content are described. An apparatus may comprise a capture module operative to record multiple data tracks from multiple sources for a multimedia event, a publishing module operative to publish the recorded multiple data tracks in a universal format, an authentication module operative to authenticate a client to access the published multiple data tracks, and a recordings management module operative to manage access to meeting content for one or more of the published multiple data tracks on a selective basis in response to client search and retrieval requests. Other embodiments are described and claimed.