Representational state transfer (REST) based geo-aware content transfer includes a REST server configured for receiving an application programming interface (API) request from a client device. The REST server obtains a upload universal resource locator (URL) targeting a caching server that is geographically closest to the client device, constructs an upload link containing the upload URL and a completion callback, and sends the upload link to the client device. The client device uses the upload URL to upload content to the caching server. The caching server interprets the completion callback to obtain a completion URL and, upon completion of content uploading, makes a REST API call using the completion URL. Responsive to the REST API call, the REST server executes an inbound operation to complete the uploading to a content management system and returns the content URL to the caching server which sends the content URL to the client device.

Representational state transfer (REST) based geo-aware content transfer includes a REST server configured for receiving an application programming interface (API) request from a client device. The REST server obtains a upload universal resource locator (URL) targeting a caching server that is geographically closest to the client device, constructs an upload link containing the upload URL and a completion callback, and sends the upload link to the client device. The client device uses the upload URL to upload content to the caching server. The caching server interprets the completion callback to obtain a completion URL and, upon completion of content uploading, makes a REST API call using the completion URL. Responsive to the REST API call, the REST server executes an inbound operation to complete the uploading to a content management system and returns the content URL to the caching server which sends the content URL to the client device.

Some embodiments provide a local controller on a set of host computers that reduce the volume of data that is communicated between the server set and the set of host computers. The local controller executing on a particular host computer, in some embodiments, receives a portion of the namespace including only the policies (e.g., opcode) that are relevant to API-authorization processing for the applications executing on the particular host computer provided by a local agent executing on the computer to authorize the API requests based on policies and parameters. The local controller analyzes the received policies (e.g., policy opcodes) and identifies the parameters (e.g. operands), or parameter types, needed for API-authorization processing (e.g., evaluating the policy opcode upon receiving a particular API request) by the local agent. In some embodiments, the local controller performs this analysis for each updated set of policies (e.g., policy opcodes).

An information handling system may identify a process identifier of a client application that has requested a connection with the information handling system. The information handling system may obtain an access control list of a process associated with the process identifier. The information handling system may determine whether to establish a connection between the client application and the information handling system based, at least in part, on analysis of the access control list.

Techniques for committing back end computing resources to an online stream of requests for data from client devices are described herein. A polling schedule server (e.g., a reservation management system), may receive polling reservation requests from a plurality of client devices, may evaluate each client device's need for “fresh” data based on a number of input signals, and may assign the client device a polling slot (e.g., a reservation for a future polling time). The polling scheduler server may subsequently receive a polling request from a client device and, upon validating a token received from the client device as well as a difference between an assigned polling time and the polling request timestamp, may grant the polling request by transmitting a request to one or more communication system servers, receiving data from the communication system servers, and providing the data to the client device.

Techniques for committing back end computing resources to an online stream of requests for data from client devices are described herein. A polling schedule server (e.g., a reservation management system), may receive polling reservation requests from a plurality of client devices, may evaluate each client device's need for “fresh” data based on a number of input signals, and may assign the client device a polling slot (e.g., a reservation for a future polling time). The polling scheduler server may subsequently receive a polling request from a client device and, upon validating a token received from the client device as well as a difference between an assigned polling time and the polling request timestamp, may grant the polling request by transmitting a request to one or more communication system servers, receiving data from the communication system servers, and providing the data to the client device.

A discovery computing system may receive an account identifier (ID) and a set of credentials required to access a first service account. The discovery computing system may transmit a first API query to a remote computing system. The discovery computing system may receive an organization identifier (ID) of the organization from the remote computing system. The discovery computing system may further transmit a second API query to the remote computing system. The discovery computing system may be further configured to receive information about a set of projects, in the organization, from the remote computing system. The discovery computing system may further generate a set of service accounts and further determine the set of resources, in the remote computing system, associated with each of the generated set of service accounts. The discovery computing system may further store the determined set of resources, as configuration items in a persistent storage.

A discovery computing system may receive an account identifier (ID) and a set of credentials required to access a first service account. The discovery computing system may transmit a first API query to a remote computing system. The discovery computing system may receive an organization identifier (ID) of the organization from the remote computing system. The discovery computing system may further transmit a second API query to the remote computing system. The discovery computing system may be further configured to receive information about a set of projects, in the organization, from the remote computing system. The discovery computing system may further generate a set of service accounts and further determine the set of resources, in the remote computing system, associated with each of the generated set of service accounts. The discovery computing system may further store the determined set of resources, as configuration items in a persistent storage.

An analytics server receives from client computing devices end-user events. Each client computing device is operated by an end-user to access an application at a web server based on the end-user events resulting in calls being passed through a proxy to the web server. The analytics server receives from the proxy the calls being made to the web server, and receives return responses from the web server being passed through the proxy. The return responses correspond to activities being performed within the application. The end-user events are correlated with the corresponding calls and return responses from the proxy. Respective correlated end-user events, calls and return responses are translated into respective event vectors. The respective event vectors are processed to determine similarities among the client computing devices. The similar activities are associated with a quality indicator to identify anomalies within the application for corrective action to be taken.

A multitenant infrastructure server (MTIS) is configured to provide an environment to execute a computer routine of an arbitrary application. The MTIS receives a request from a webtask server to execute the computer routine in a webtask container. The computer routine is executed in the webtask container at the MTIS. Upon successful execution of the computer routine, a result set is returned to the webtask server. If the execution of the computer routine is unsuccessful, an error notification is returned to the webtask server. The resources consumed during the execution of the computer routine are determined. The webtask container is destroyed to prevent persistent storage of the computer routine on the MTIS.