Abstract: The latency corresponding to a latency-sensitive event-based processor is evaluated to determine whether the latency-sensitive event-based processor (EBP) should be prioritized. If so, constraints on the number of events that the latency-sensitive EBP can process are relaxed and the frequency with which the latency-sensitive EBP can process events is increased. At a next latency evaluation, if the latency-sensitive EBP no longer meets criteria for prioritization, the constraint on the number of events is returned to a nominal level, as is the frequency with which the latency-sensitive EBP can process events.

Abstract: A server kernel processing system receives an input/output (I/O) request from a user mode computing environment. The I/O request is analyzed to determine whether it is a file open request. If so, target analysis logic determines whether the file open request is for a driver file or for a file within a protected volume that stores a driven whitelist file. If the file open request is for a file stored in a protected volume, the request is blocked. If the file open request is for a driver file, then the driver whitelist file is examined to determine whether the target driver is on the whitelist. If not, the file open request is also blocked.

Abstract: A server kernel processing system receives an input/output (I/O) request from a user mode computing environment. The I/O request is analyzed to determine whether it is a file open request. If so, target analysis logic determines whether the file open request is for a driver file or for a file within a protected volume that stores a driven whitelist file. If the file open request is for a file stored in a protected volume, the request is blocked. If the file open request is for a driver file, then the driver whitelist file is examined to determine whether the target driver is on the whitelist. If not, the file open request is also blocked.

Abstract: Dynamic deferral systems and methods providing a means to defer performance of a task for a distributed computing system entity both by the number of work cycles as well as in response to an occurrence of a triggering event. By deferring the scheduling in terms of the number of work-cycles, the memory footprint is reduced as the scheduling matrix uses only one byte to store the number. This approach also takes advantage of the most significant bit of a byte to indicate whether the scheduled job is to be evoked in response to a triggering event.

Abstract: The latency corresponding to a latency-sensitive event-based processor is evaluated to determine whether the latency-sensitive event-based processor (EBP) should be prioritized. If so, constraints on the number of events that the latency-sensitive EBP can process are relaxed and the frequency with which the latency-sensitive EBP can process events is increased. At a next latency evaluation, if the latency-sensitive EBP no longer meets criteria for prioritization, the constraint on the number of events is returned to a nominal level, as is the frequency with which the latency-sensitive EBP can process events.

Abstract: A calendar application on a communication device generates a user interface that allows a user to interact with a representation of a calendar event. The calendar application detects a user configuration input indicative of how to control the communication device, in responding to a real-time communication event, during the calendar event. When the real-time communication event is detected during the calendar event, the calendar application controls the communication device based upon the configuration input.

Abstract: Dynamic deferral systems and methods providing a means to defer performance of a task for a distributed computing system entity both by the number of work cycles as well as in response to an occurrence of a triggering event. By deferring the scheduling in terms of the number of work-cycles, the memory footprint is reduced as the scheduling matrix uses only one byte to store the number. This approach also takes advantage of the most significant bit of a byte to indicate whether the scheduled job is to be evoked in response to a triggering event.

Abstract: A server kernel processing system receives an input/output (I/O) request from a user mode computing environment. The I/O request is analyzed to determine whether it is a file open request. If so, target analysis logic determines whether the file open request is for a driver file or for a file within a protected volume that stores a driven whitelist file. If the file open request is for a file stored in a protected volume, the request is blocked. If the file open request is for a driver file, then the driver whitelist file is examined to determine whether the target driver is on the whitelist. If not, the file open request is also blocked.