Abstract: An application management system using Remote Procedure Call (RPC) frameworks can easily consume excessive amounts of memory or other resources. As described herein, tasks are allocated and balanced amongst engines using a small or fixed size of volatile memory. The memory used in such systems can balance tasks or jobs between different engines by allocating tasks between engine task lists. The complete details of those tasks are stored in queues in non-volatile memory. Tasks are allocated among the lists using a set of rules for new work, pinned work, work from disconnected engines, and reallocated work. The quantity of volatile memory and other resources necessary to manage the RPC framework is thereby reduced, or can even be handled within a size of volatile memory fixed by the user.

Abstract: An example computer system for providing a communication system can include: one or more processors; and non-transitory computer-readable storage media encoding instructions which, when executed by the one or more processors, causes the computer system to: monitor criteria associated with the communication system; assign a weight to the criteria to determine a risk score associated with the communication system; and automatically change an address of the communication system when the risk score exceeds a threshold.

Abstract: An application management system using Remote Procedure Call (RPC) frameworks can include enhancements. These enhancements can be used on files that are distributed to engines throughout the RPC framework. Enhancements can be stored in an enhancement server. The enhancements can include password detection, logo detection, cleartext detection, or other checks or modifications that may be useful to a variety of engines in the RPC framework. The enhancements can be used to ensure that unencrypted sensitive data, passwords, or files with confidential information (as indicated by logos or other pictorial markings) are not distributed throughout the RPC framework.

Abstract: An example computer system for providing a communication system can include: one or more processors; and non-transitory computer-readable storage media encoding instructions which, when executed by the one or more processors, causes the computer system to: monitor criteria associated with the communication system; assign a weight to the criteria to determine a risk score associated with the communication system; and automatically change an address of the communication system when the risk score exceeds a threshold.

Abstract: An example computer system for providing a communication system can include: one or more processors; and non-transitory computer-readable storage media encoding instructions which, when executed by the one or more processors, causes the computer system to: monitor criteria associated with the computer system; calculate a risk score associated with the communication system; and automatically change one or more endpoints of the computer system when the risk score exceeds a threshold.

Abstract: An application management system using Remote Procedure Call (RPC) frameworks can include enhancements. These enhancements can be used on files that are distributed to engines throughout the RPC framework. Enhancements can be stored in an enhancement server. The enhancements can include password detection, logo detection, cleartext detection, or other checks or modifications that may be useful to a variety of engines in the RPC framework. The enhancements can be used to ensure that unencrypted sensitive data, passwords, or files with confidential information (as indicated by logos or other pictorial markings) are not distributed throughout the RPC framework.

Abstract: An example computer system for providing a communication system can include: one or more processors; and non-transitory computer-readable storage media encoding instructions which, when executed by the one or more processors, causes the computer system to: monitor criteria associated with the communication system; assign a weight to the criteria to determine a risk score associated with the communication system; and automatically change an address of the communication system when the risk score exceeds a threshold.

Abstract: An application management system using Remote Procedure Call (RPC) frameworks can include enhancements. These enhancements can be used on files that are distributed to engines throughout the RPC framework. Enhancements can be stored in an enhancement server. The enhancements can include password detection, logo detection, cleartext detection, or other checks or modifications that may be useful to a variety of engines in the RPC framework. The enhancements can be used to ensure that unencrypted sensitive data, passwords, or files with confidential information (as indicated by logos or other pictorial markings) are not distributed throughout the RPC framework.

Abstract: An application management system using Remote Procedure Call (RPC) frameworks can easily consume excessive amounts of memory or other resources. As described herein, tasks are allocated and balanced amongst engines using a small or fixed size of volatile memory. The memory used in such systems can balance tasks or jobs between different engines by allocating tasks between engine task lists. The complete details of those tasks are stored in queues in non-volatile memory. Tasks are allocated among the lists using a set of rules for new work, pinned work, work from disconnected engines, and reallocated work. The quantity of volatile memory and other resources necessary to manage the RPC framework is thereby reduced, or can even be handled within a size of volatile memory fixed by the user.