Methods, systems, and apparatus, including computer programs encoded on computer storage media, for memory requests by a virtual machine. One of the methods includes generating a plurality of doorbell pages for a plurality of virtual machines executing on a device, providing, to each of the plurality of virtual machines, access to a respective one of the plurality of doorbell pages that identifies a queue that stores requests from the respective virtual machine, receiving, from a particular one of the plurality of doorbell pages, a notification that the respective queue has a request from the respective virtual machine, and in response to receiving the notification that the respective queue has a request from the respective virtual machine, causing a processor to process the respective queue for the respective virtual machine.

A method for managing a trigger on a terminal device, and a terminal device are provided. In response to an operation (S301) of setting a trigger by an application program (181), a trigger manager (235) determines a triggering policy of the trigger based on a use habit of a user, characteristic information of the trigger, and characteristic information of the application program. The triggering policy is accelerating triggering, normal triggering, or delaying triggering. Different triggering policies are executed for triggers having different characteristics, to dynamically change timings for the triggers to trigger scheduled tasks. In this way, a malicious trigger configured to keep an application alive or trigger a task that does not match a true will of the user is prevented to reduce resource consumption, and a trigger beneficial to a system or the user can be triggered earlier to improve user experience.

An information exchange between at least two processes (FEED_PROC-1, FEED_PROC-2, CONSUME_PROC-1) communicating with each other using at least one queue (QUEUE-001) uses a placement plan for determining the order in which messages are placed into the queue. The information feeding processes (FEED_PROC-1, FEED_PROC-2) place pieces of information (MESG-001, MESG-002) into the queue (QUEUE-001), from where an information consuming process (CONSUME_PROC-1) sequentially consumes the pieces of information. The placement plan describes, for at least one possible value of identifying information contained in each of the pieces of information, a respective position (POS-001, POS-002) in the queue (QUEUE-001), such that the pieces of information (MESG-001, MESCG-002) or respective references thereto are placed into the queue according to positions in the queue (QUEUE-001) corresponding to the respective values of the identifying information in the pieces of information.

The described technology relates to a publish-subscribe message framework in which an application, decomposed to a plurality of processing stages, is run by executing respective processing stages of the application asynchronously and simultaneously with each other. Communications between the respective processing stages may exclusively be in accordance with the publish-subscribe execution model. The described publish-subscribe framework provides for processing stages to be executed in a multi-process and/or multi-threaded manner while also enabling the distribution of the processing stages to respective processing resources in a multi-processor/multi-core processing environment. An example electronic exchange application and a corresponding example exchange gateway application are described.

In a system and method for accessing messages in a data store in a gateway, a data frame request, which is a structured SQL query, is received at the gateway. The received data frame request is applied to the gateway data store, which stores messages. A data frame is generated that comprises messages from the data store that are responsive to the received data frame request, the data frame having a format that is readable by a character editor.

An electronic device displays one or more views. A first view includes a plurality of gesture recognizers. The plurality of gesture recognizers in the first view includes one or more proxy gesture recognizers and one or more non-proxy gesture recognizers. Each gesture recognizer indicates one of a plurality of predefined states. A first proxy gesture recognizer in the first view indicates a state that corresponds to a state of a respective non-proxy gesture recognizer that is not in the first view. The device delivers a respective sub-event to the respective non-proxy gesture recognizer that is not in the first view and at least a subset of the one or more non-proxy gesture recognizers in the first view. The device processes the respective sub-event in accordance with states of the first proxy gesture recognizer and at least the subset of the one or more non-proxy gesture recognizers in the first view.

The present disclosure generally discloses an event handling capability configured to support handling of events. The event handling capability may be configured to support handling of events in a distributed event handling system, which may use distributed queuing of events, distributed processing of events, and so forth. The distributed event handling system may be serverless cloud system or other type of distributed event handling system. The event handling capability may be configured to support handling of events in a distributed event handling system based on use of a message bus for queuing of events and based on use of hosts for queuing and processing of events.

Embodiments of the present disclosure relate to a broadcast control method and apparatus, and a terminal device. The method includes: when the one or more application programs run on a background and meet a first preset condition, sending a first control instruction; and when the first control instruction is received, freezing and buffering a broadcast to be sent to the one or more application programs.

An electronic device displays one or more views. A first view includes a plurality of gesture recognizers. The plurality of gesture recognizers in the first view includes one or more proxy gesture recognizers and one or more non-proxy gesture recognizers. Each gesture recognizer indicates one of a plurality of predefined states. A first proxy gesture recognizer in the first view indicates a state that corresponds to a state of a respective non-proxy gesture recognizer that is not in the first view. The device delivers a respective sub-event to the respective non-proxy gesture recognizer that is not in the first view and at least a subset of the one or more non-proxy gesture recognizers in the first view. The device processes the respective sub-event in accordance with states of the first proxy gesture recognizer and at least the subset of the one or more non-proxy gesture recognizers in the first view.

According to certain embodiments, a provisioning manager comprises an interface and processing circuitry. The interface is configured to obtain provisioning data from a provisioning database. The processing circuitry is configured to prepare one or more configuration files based on the provisioning data. The configuration file(s) indicate how to provision one or more service instances. The processing circuitry is further configured to commit the configuration file(s) to one or more repositories in order to make the configuration file(s) available to at least one of the service instances. The processing circuitry is further configured to send one or more notifications indicating to one or more of the service instances that the configuration file(s) have been committed to the one or more repositories.