Technology for determining whether an inter-process type message has been successfully sent from a first process to a second process running on a single computer with a single processor(s) set. A variable (for example, a bit value) is used to indicate whether the inter-process message has been communicated between the processes. A timer and a predetermined timeout threshold are used to determine if the inter-process message has been pending for too long without being successfully communicated.

A method for directing messages between a composite user interface and at least one source application. A message is to be directed to a predetermined set of services, each service executes a command specified by the message and the message comprises details of the predetermined set of services. Each service in the predetermined set of services uses said details to determine whether the message should be sent to another service, and if it is determined that the message should be sent to another service transmits the message to an appropriate service.

A system and a method for providing resiliency in a telephony communication system are provided. The method includes: receiving registration information that relates to a requested service, the registration information including a service name, a resource identifier such as a directory number, at least one pool, and status information; and mapping the received registration information to a database that associates the name of the requested service with the resource identifier and each pool and associates each pool with the status information; and transmitting at least two Uniform Resource Locators (URLs), including a primary URL and a backup URL, for providing the requested service.

This document discloses techniques, apparatuses, and systems for inter-service communication management to manage inter-service communication between a server-side service and a client-side service. The inter-service management system may comprise memory and a controller configured to perform the inter-service communication management. In aspects, a configuration file may be used to obtain information specifying a first inter-service communication mechanism for communicating one or more messages between the client-side and server-side services. The inter-service communication management system may instantiate a stub associated with the inter-service communication mechanism information, which can be used to communicate a message from the server-side service to a proxy that interacts with the client-side service. The message may then be forwarded from the proxy to the client-side service to enable inter-service communication between the server-side service and the client-side service.

A method and apparatus for an extensible, format-independent middleware message interpreter is disclosed in which a host machine is configured with a universal message service (UMS). The UMS communicates with local and cloud servers and destination devices. The UMS is configured with a plug-in service that can accommodate plug-in libraries of plug-in modules. The UMS receives formatted messages from the local and cloud server applications and destination devices, parses the messages, and identifies a command message type. Based on the command message type, the UMS performs actions including executing the local command on the host machine, relaying the embedded-sub-message data to the at least one destination device as indicated by the destination identification, and relaying the embedded-sub-message data to the plug-in service.

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.

A modular image processing SDK comprises an API to receive API calls from third party software running on a portable device including a camera. SDK logic receives and processes commands and parameters received from the API that are based on the API calls received from the third party software. An annotation system performs image processing operations on a feed from the camera based on image processing instructions and parameters received by the annotation system from the SDK logic. The image processing is based at least in part on augmented reality content generator data (or AR content generators), user input and sensor data.

The present disclosure provides an exception stack handling method, system, electronic device and storage medium and relates to the field of mobile Internet. The method may include: at the level of any executor in a distributed stream-type processing system including at least two executors, performing the following processing of: obtaining at least one exception stack from a message middleware when the executor in an idle state each time, collected exception stacks generated by users being stored in the message middleware; as for any exception stack, obtaining an anti-obfuscation map file corresponding to the exception stack, and performing anti-obfuscation processing for the exception stack by using the anti-obfuscation map file. The solution of the present disclosure may be applied to improve the processing speed.

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.

A method includes creating a publisher configured to send messages over a channel having a shared memory. The method includes creating at least one subscriber configured to receive the messages over the channel by sequentially referencing memory slots of the plurality of memory slots. The method includes determining that the next sequential memory slot is currently referenced by a subscriber. The method includes delaying sending the message by the publisher based on determining that the next sequential memory slot is currently referenced by the subscriber. The method includes receiving an event trigger indicative of message reading by the subscriber. The method includes, responsive to receiving the event trigger, determining that the next sequential memory slot is not currently referenced. The method includes sending the message to the next sequential memory slot based on determining that the next sequential memory slot is not currently referenced.