In an application execution system having a plurality of application servers, each application server stores a plurality of applications, and has computational resources for executing applications in response to received requests. Each application server also includes instructions for loading a respective application into volatile storage and executing the application in response to a request from a client, and for returning a result. A generic application instance may be cloned, creating a pool of generic application instance clones that can be loaded with code for a requested application to produce an application instance. The application instance can then be stored in a cache to be used for a future application request.

A method, apparatus, electronic device, storage medium and program product of code management are provided. In response to a request for building an executable file, corresponding developed code is obtained from a code library. The developed code is compiled into intermediate code to determine security of the intermediate code. In response to determining that the intermediate code is secure, an executable file is generated based on the intermediate code.

Embodiments of the present disclosure enable users of a data sharing system to build native applications that can be shared with other users of the data sharing system. The native applications can be published and discovered in the data sharing system like any other data listing, and consumers can install them in their local data sharing system account to serve their data processing needs. A provider may define an installation script for installing an application and create a share object to which the installation script may be attached. In response to an imported database being created in a consumer account based on the share object, a native application framework may automatically execute the installation script in the consumer account and may create a set of database roles to manage execution of the application in the consumer account.

The subject technology provides a portion of the functionality of an application on an electronic device on which the application is not installed. The portion of the functionality of the application is provided by a clip of the application that can be obtained, installed, and launched on the user device, at the time the functionality is desired by a user, and without authenticating information for the user. The clip of the application can provide the user with access to a purchase function, an ordering function, or any other sub-function of the application. When the application itself is installed on the device, the clip of the application can be deleted while preserving access, by the application, to data generated on the device by the clip.

The subject technology provides a portion of the functionality of an application on an electronic device on which the application is not installed. The portion of the functionality of the application is provided by a clip of the application that can be obtained, installed, and launched on the user device, at the time the functionality is desired by a user, and without authenticating information for the user. The clip of the application can provide the user with access to a purchase function, an ordering function, or any other sub-function of the application. When the application itself is installed on the device, the clip of the application can be deleted while preserving access, by the application, to data generated on the device by the clip.

Techniques for managing licensing of a software application that includes a plurality of executables are presented. The techniques can include detecting an initiation of the software application on a client computer; obtaining a license for a usage of a first executable of the plurality of executables; detecting an initiation of at least a second executable; obtaining execution type data for the second executable specifying one of: a license for a usage of the second executable is not required if an instance of the second executable is executing on the client computer, or a license for a usage of the second executable is not required if at least one executable of the plurality of executables is executing on the client computer; determining, based on the execution type data, that a license for a usage of the second executable is not required; and executing the second executable.

Techniques for managing licensing of a software application that includes a plurality of executables are presented. The techniques can include detecting an initiation of the software application on a client computer; obtaining a license for a usage of a first executable of the plurality of executables; detecting an initiation of at least a second executable; obtaining execution type data for the second executable specifying one of: a license for a usage of the second executable is not required if an instance of the second executable is executing on the client computer, or a license for a usage of the second executable is not required if at least one executable of the plurality of executables is executing on the client computer; determining, based on the execution type data, that a license for a usage of the second executable is not required; and executing the second executable.

Adjusting wireless docking resource usage, including identifying, at a client information handling system (IHS), a configuration policy, the client IHS wirelessly connected to a docking station, the docking station providing wireless connections to peripheral computing components, respectively; processing, at the client IHS, the configuration policy, including identifying configuration rules of the configuration policy for performing computer-implemented actions of throttling resource utilization between the client IHS and the docking station; identifying, at the client IHS, when the client IHS is wirelessly connected to the docking station, a first presence state of a user with respect to the client IHS; and determining, at the client IHS, that the first presence state indicates that the user of the client IHS is not actively engaged with the client IHS, and in response, applying the configuration rules to perform computer-implemented actions of throttling resource utilization between the client IHS and the docking station.

An information handling system may include at least one processor, and a non-transitory memory coupled to the at least one processor. The information handling system may be configured to execute a configuration procedure to set up a plurality of information handling resources of the information handling system, and wherein the configuration procedure includes a plurality of logical groups related to different types of configuration. Each logical group may include one or more atomic groups, each atomic group including a plurality of logically related atomic operations. In response to a failure of a particular atomic operation of a particular atomic group, the information handling system may be configured to roll back the particular atomic operation and allow the configuration procedure to be restarted at a beginning of the particular atomic group.

The present invention includes computerized method and apparatus for user interactivity with a network application executing on a server. The method and apparatus includes receiving, via a wireless network, an event message from a mobile device, the event message representing an input from a user interface on the mobile device where the user interface is executing based on a mobile application. The method and apparatus further includes generating data values based on the input in the event message and information relating to the mobile device. Moreover, the method and apparatus includes sending an update message to the mobile device based on the data values for updating a display of the mobile device.