G06F9/44521

Hot reloading a running application with an unsaved source code change

Hot reloading a running application with an unsaved source code change. A code change to a source code of a running software application that is associated with a project type is identified. The code change is stored within an in-memory editor buffer, and is uncommitted to any source code file. It is determined that the code change can be applied to the running software application using hot reload. Hot reload agent(s) associated with the project type are identified. Using the hot reload agent(s), the code change is communicated to an application runtime associated with the running software application. At least one process of the running software application invokes a new compiled code entity corresponding to the code change.

METHOD AND ELECTRONIC DEVICE FOR MANAGING A BOOST TIME REQUIRED FOR AN APPLICATION LAUNCH

A method for managing a boost time required for an application launch in an electronic device is provided. The method includes detecting, by the electronic device, a user input to launch the application. Further, the method includes measuring, by the electronic device, real-time system health parameters of the electronic device. Further, the method includes predicting, by the electronic device, an application launch time by inputting the real-time system health parameters to an AI-based application prediction model. Further, the method includes boosting, by the electronic device, at least one hardware of the electronic device based on the predicted application launch time.

WEBPAGE LOADING METHOD AND SYSTEM
20180004857 · 2018-01-04 ·

Webpage loading method and system. While browsing a webpage, a user can uninterruptedly browse subsequent contents without waiting for page loading since whether subsequent pages need to be loaded is determined by the prediction of remaining page browsing time. The method comprises: in response to a page loading completion event, recording a current page end scroll bar value, a current page initial scroll bar value and a current page loading completion moment; in response to a scroll bar scrolling event, recording a present scroll bar triggering moment and a present scroll bar value; calculating a page browsing speed and a remaining page browsing time; and when the remaining page browsing time meets a preset condition, sending to a server a page acquisition request related to subsequent pages of the current page and loading and updating page data about the subsequent pages to the end of the current page.

COMPONENT LOADING BASED ON USER INTERACTIONS

Provided herein are systems, methods, and software for implementing information management applications. In an implementation, an application embodied in program instructions stored on one or more computer readable storage media comprises components and a control component. The components communicate requests to invoke others of the components. The control component handles the requests by at least determining whether or not any component identified by the requests has already been downloaded or is yet to be downloaded. The control component invokes the component when already downloaded and retrieves the component when not yet downloaded.

Systems and methods for developing digital experience applications

In one implementation, systems and methods are provided for developing a computer-implemented digital experience application having a first and a second micro-application. Each micro-application includes a front end interface configured to receive and display information. The first micro-application includes a first event manager configured to detect an application event belonging to a category, and a first state manager configured to detect an application state belonging to the category. The digital experience application further includes a driver application configured to host the first and second micro-applications, an event hub configured to receive the detected application event from the first micro-application, and a state store configured to store the detected application state received from the first micro-application. The second micro-application includes a second event manager configured to receive the detected application event from the event hub, and a second state manager configured to receive the detected application state from the state store.

Shadow stack violation enforcement at module granularity

Enforcing shadow stack violations at module granularity, rather than at thread or process granularity. An exception is processed during execution of a thread based on code of an application binary, which is enabled for shadow stack enforcement, that calls an external module. The exception results from a mismatch between a return address popped from the thread's call stack and a return address popped from the thread's shadow stack. Processing the exception includes determining that the exception resulted from execution of an instruction in the external module, and determining whether or not the external module is enabled for shadow stack enforcement. Based at least on these determinations, execution of the thread is terminated when the external module is enabled for shadow stack enforcement, or the thread is permitted to continue executing when the external module is not enabled for shadow stack enforcement.

Web component dynamically deployed in an application and displayed in a workspace product

Provided are computer-implemented methods and systems for dynamically deploying a web component in an application. An example method for dynamically deploying a web component in an application may include deploying a client-side application to a web browser associated with a client device. The method may continue with receiving a request to deploy a web component in the client-side application. The method may further include dynamically loading the web component in the client-side application. With this method, web components can be dynamically added to a current operating version of a web application. Further, a user can use a web application as if it is operating locally on the web browser of the client device, even though it is not actually stored locally on the client device.

Technique for reporting nested linking among applications in mainframe computing environment
11714662 · 2023-08-01 · ·

A computer-implemented method is presented for reporting application programs linked to by an application running under an online transaction processor of a mainframe computing environment. An intercept program is implanted in an address space of the online transaction processor. A task executing outside of the address space of the online transaction processor identifies an address for a target domain gate program supported in a domain by the online transaction processor; identifies an address for an unused domain gate program supported in the domain by the online transaction processor; replaces the address for the unused domain gate program with the address for the target domain gate program; and replaces the address for the target domain gate program with an address for the intercept program.

METHOD AND APPARATUS FOR IDENTIFYING DYNAMICALLY INVOKED COMPUTER CODE
20230229460 · 2023-07-20 ·

A method, computerized apparatus and computer program product, the method comprising: obtaining user code; using static analysis, determining from the user code a collection of components upon which the user code depends, the collection of components comprising a first component representing a first entity, wherein one or more components of the collection of components is to be loaded dynamically by the user code; determining whether the user code or the first component from the collection of components uses dynamic invocation; subject to the user code or the first component using dynamic invocation, adding a new connection to a second component from the collection of components, the second component representing a second entity that augments an entity reachable from the first entity; and outputting information about the second entity.

Method and system for generating and rendering a customized dashboard

This disclosure relates to method and system for generating and rendering a customized dashboard. The method includes initiating a schema-less dashboard canvas through a frontend application that invokes a server-less library. The method further includes integrating a set of widgets selected by a user, from the plurality of native widgets and from the plurality of third-party widgets, with the schema-less dashboard canvas using the server-less library. The method further includes generating metadata for each of the set of widgets based on a corresponding configuration performed by the user. The method further includes associating the metadata with a user account of the user for subsequent rendering of the customized dashboard for the user.