Various implementations for expedited processing and handling of events are described. A first event associated with a set of one or more surfaces rendered for display in a multi-dimensional space is detected. The first event is routed to a first set of one or more event processors for processing. The first event is processed using the first set of one or more event processors and after the processing, the first event is handled using one or more first event handlers.

Provided is a terminal apparatus including a display unit displaying an execution screen of a shared application, reflecting on a display operations performed by multiple users as operations performed on one application, where the shared application includes a function for displaying an identification object that associates each of the users with an operation result, displayed on the execution screen, reflecting the operation performed by each of the users, a function for setting, when a first user selects an identification object related to a second user and specifies a region on the screen, the specified region as a shared region that is shared by the first and second users, and a function for controlling, when the first or second user performs operation in the shared region, such that the displayed operation result reflecting the operation is not shown to users other than the first and second users.

An abstract data graph may be constructed at a server. The abstract data graph may include nodes and links between nodes and may represent computer programming instructions for generating a graphical user interface at a client machine. At least some of the links may represent dependency relationships between portions of the graphical user interface. The abstract data graph may be resolved at the client machine to identify data items, which may be retrieved from the server and used to render the graphical user interface.

An abstract data graph may be constructed at a server. The abstract data graph may include nodes and links between nodes and may represent computer programming instructions for generating a graphical user interface at a client machine. At least some of the links may represent dependency relationships between portions of the graphical user interface. The abstract data graph may be resolved at the client machine to identify data items, which may be retrieved from the server and used to render the graphical user interface.

Techniques and systems are provided for processing user interface content. For example, a server computer can receive a user interface event corresponding to a user interface of a device (e.g., a client device, another server computer, or other device). An application associated with the user interface evet can be determined, and an interface model 5 can be generated using the application associated with the user interface evet. The interface model defines state information for one or more graphic objects of the user interface. The state information results from the user interface event. The server computer can send the interface model to the device, which enables the device to render the user interface.

Implementations set forth herein relate to intervening notifications provided by an application for mitigating computationally wasteful application launching behavior that is exhibited by some users. A state of a module of a target application can be identified by emulating user inputs previously provided by the user to the target application. In this way, the state of the module can be determined without visibly launching the target application. When the state of the module is determined to satisfy criteria for providing a notification to the user, the application can render a notification for the user. The application can provide intervening notifications for a variety of different target applications in order to reduce a frequency at which the user launches and closes applications to check for variations in target application content.

In non-limiting examples of the present disclosure, systems, methods and devices for filtering notifications are provided. A notification may be received. A current focus state of a user may be determined. An application priority score for the application that generated the notification may be determined. A notification priority score for the notification may be determined. The notification priority score may be determined based on a contact importance score and/or a content importance score. A combined priority score may be determined from the application priority score and the notification priority score. The notification may be surfaced if the combined priority score meets a threshold surfacing value. The notification may be blocked if the combined priority score does not meet the threshold surfacing value.

Each of a plurality of wire web components predicted to be included in a graphical user interface (GUI) for presentation at a client machine. Each data object instance may be associated with a respective data object instance identifier and a respective one or more data object fields. A wire web component graph that includes a plurality of nodes may be constructed. A node may correspond to a wire web component, a data object field, or an application procedure interface (API). One or more of the data values may be retrieved from the respective APIs based on the wire web component graph. A GUI message including the retrieved data values and the wire web component graph may be transmitted to the client machine.

Systems and methods of implementing a finite-state machine using electronic notifications delivered to a client device in a computer networking environment are provided. A content item can be received, along with first and second notifications associated with the content item. The first and second notifications can be stored in a queue. In some implementations, a state machine can be maintained in which at least some states may cause the first or second notifications to be displayed, and in which transitional conditions between states may depend at least in part on user interaction with the displayed notifications.

A method for reading and writing clipboard information, applied to a terminal, includes: acquiring a request for reading and writing clipboard information; determining a read permission for clipboard information, in response to the request for reading and writing clipboard information including a request for reading clipboard information, and allowing to read the clipboard information or refusing to read the clipboard information based on the read permission; and determining a write permission for the clipboard information, in response to the request for reading and writing clipboard information including a request for writing clipboard information, and allowing or refusing to write the clipboard information based on the write permission. The read and write permission of the clipboard can be divided into the read permission and the write permission, thereby facilitating preventing leakage of the clipboard information in the clipboard and improving the security of the clipboard information.