Abstract: A data processing network includes a database management for a plurality of databases serviced by a server comprising a plurality of data processors. Each server data processor includes a copy of the database management system and a monitor for measuring and analyzing various parameters for each server data processor and each included database and performing various methods transparently to a user. For example, when a parameter or combination thereof indicates that a database in one data processor is inactive or requires additional resources, that database is set to an inactive state or is transferred to another data processor with greater resources, respectively. An inactive database is recalled upon receipt of a request for access to that database. A database in a data processor of greater resources can be returned to a server data processor or another data processor with fewer resources. These operations are transparent to database users and independent of user or administrator intervention.

Abstract: A system and method for accessing data suitable for controlling user access to data across a shared distributed storage system is provided. The present invention relates to a system and method for a data management service that captures context for accessed data and utilizes the captured context with operational policy to govern user access to the data.

Abstract: A data processing network includes a database management for a plurality of databases serviced by a server comprising a plurality of data processors. Each server data processor includes a copy of the database management system and a monitor for measuring and analyzing various parameters for each server data processor and each included database and performing various methods transparently to a user. For example, when a parameter or combination thereof indicates that a database in one data processor is inactive or requires additional resources, that database is set to an inactive state or is transferred to another data processor with greater resources, respectively. An inactive database is recalled upon receipt of a request for access to that database. A database in a data processor of greater resources can be returned to a server data processor or another data processor with fewer resources. These operations are transparent to database users and independent of user or administrator intervention.

Abstract: A data processing network includes a database management for a plurality of databases serviced by a server comprising a plurality of data processors. Each server data processor includes a copy of the database management system and a monitor for measuring and analyzing various parameters for each server data processor and each included database and performing various methods transparently to a user. For example, when a parameter or combination thereof indicates that a database in one data processor is inactive or requires additional resources, that database is set to an inactive state or is transferred to another data processor with greater resources, respectively. An inactive database is recalled upon receipt of a request for access to that database. A database in a data processor of greater resources can be returned to a server data processor or another data processor with fewer resources. These operations are transparent to database users and independent of user or administrator intervention.

Abstract: A data processing network includes a database management for a plurality of databases serviced by a server comprising a plurality of data processors. Each server data processor includes a copy of the database management system and a monitor for measuring and analyzing various parameters for each server data processor and each included database and performing various methods transparently to a user. For example, when a parameter or combination thereof indicates that a database in one data processor is inactive or requires additional resources, that database is set to an inactive state or is transferred to another data processor with greater resources, respectively. An inactive database is recalled upon receipt of a request for access to that database. A database in a data processor of greater resources can be returned to a server data processor or another data processor with fewer resources. These operations are transparent to database users and independent of user or administrator intervention.

Abstract: Disclosed herein is a system and method for dynamic scheduling of application tasks in a distributed task-based system. The system and method employ a learning mechanism that observes and predicts overall application task costs across a networked system, taking into account how the states or loads of the applications are likely to change over time. The application task costs are defined in economic terms. The system and method allows continuous optimization of application response times as perceived by application users.

Abstract: One embodiment may estimate the processing time of tasks requested by an application by maintaining a state-model for the application. The state model may include states that represent the tasks requested by the application, with each state including the average run-time of each task. In another embodiment, a state model may estimate which task is likely to be requested for processing after the current task is completed by providing edges in the state model connecting the states. Each edge in the state model may track the number of times the application transitions from one task to the next. Over time, data may be gathered representing the percentage of time that each edge is from a state node. Given this information, the scheduler may estimate the CPU cost of the next task based on the current state, the most likely transition, and the cost of the predicted next task.

Abstract: One embodiment may estimate the processing time of tasks requested by an application by maintaining a state-model for the application. The state model may include states that represent the tasks requested by the application, with each state including the average run-time of each task. In another embodiment, a state model may estimate which task is likely to be requested for processing after the current task is completed by providing edges in the state model connecting the states. Each edge in the state model may track the number of times the application transitions from one task to the next. Over time, data may be gathered representing the percentage of time that each edge is from a state node. Given this information, the scheduler may estimate the CPU cost of the next task based on the current state, the most likely transition, and the cost of the predicted next task.

Abstract: Disclosed herein is a system and method for dynamic scheduling of application tasks in a distributed task-based system. The system and method employ a learning mechanism that observes and predicts overall application task costs across a networked system, taking into account how the states or loads of the applications are likely to change over time. The application task costs are defined in economic terms. The system and method allows continuous optimization of application response times as perceived by application users.

Abstract: A system and method are provided for streaming a media track to multiple clients using a single copy of the track's metadata, rather than making separate copies of the metadata for each stream. A media track's metadata includes information that is used to identify and locate media corresponding to different time positions in the track or media program. Sharing one copy of the metadata among multiple client streams promotes more efficient use of a media streaming server's resources. When a media track is first requested, a track object is generated to store and allow access to the metadata. For each client stream, a separate track handle object is created to manage access to the metadata for the stream's specific context. The streamed media track may be part of a live media event or may be part of a pre-recorded media program.

Abstract: A method and apparatus are provided for handling events received at a media streaming server. Server sockets configured to receive events are divided into collections and registered with a polling object. Each collection shares a processor thread for detecting events. Each socket is associated with an event consumer object that is notified when an event is received at the socket. The event consumer objects invoke task objects to handle the events. Task objects are queued in a task queue and execute using a pool of processor threads. Event consumer objects are derived from an abstract base consumer class that defines a common interface. Subclasses of the base consumer class are configured for different types of events that may be received (e.g., connection requests, media streaming commands, media data, media stream quality reports). Specific event consumer objects are instantiated from the subclasses to provide implementations of the common interface.

Abstract: A system and method are provided for resynchronizing a media stream. A media streaming server receives live or pre-recorded media for streaming to clients. When media is not received or available for streaming at the appropriate media time index, the media stream is deemed to be out of synchronization. The server selects a future time index at which to resynchronize the stream and may discard intervening media. Media corresponding to the new time index is requested or retrieved and, if available at the new time index, media streaming resumes in synchronization. If media corresponding to the new time index is not available, the server may select another future time index and try again to resynchronize. Resynchronization may be attempted a configurable number of times and, if unsuccessful, the server may terminate the stream.

Abstract: A system and method are provided for streaming a media track to multiple clients using a single copy of the track's metadata, rather than making separate copies of the metadata for each stream. A media track's metadata includes information that is used to identify and locate media corresponding to different time positions in the track or media program. Sharing one copy of the metadata among multiple client streams promotes more efficient use of a media streaming server's resources. When a media track is first requested, a track object is generated to store and allow access to the metadata. For each client stream, a separate track handle object is created to manage access to the metadata for the stream's specific context. The streamed media track may be part of a live media event or may be part of a pre-recorded media program.

Abstract: A system and method are provided for resynchronizing a media stream. A media streaming server receives live or pre-recorded media for streaming to clients. When media is not received or available for streaming at the appropriate media time index, the media stream is deemed to be out of synchronization. The server selects a future time index at which to resynchronize the stream and may discard intervening media. Media corresponding to the new time index is requested or retrieved and, if available at the new time index, media streaming resumes in synchronization. If media corresponding to the new time index is not available, the server may select another future time index and try again to resynchronize. Resynchronization may be attempted a configurable number of times and, if unsuccessful, the server may terminate the stream.

Abstract: A method and apparatus are provided for handling events received at a media streaming server. Server sockets configured to receive events are registered with a polling object and may be divided into collections. Each collection shares a processor thread for detecting events. Each socket is associated with an event consumer object that is notified when an event is received at the socket. The event consumer objects invoke task objects to handle the events. Task objects are queued in a task queue and execute using a pool of processor threads. Event consumer objects are derived from an abstract base consumer class that defines a common interface. Subclasses of the base consumer class are configured for different types of events that may be received (e.g., connection requests, media streaming commands, media data, media stream quality reports). Specific event consumer objects are instantiated from the subclasses to provide implementations of the common interface.