Provided is a method of processing remote procedure calls (RPCs), the method including receiving a first RPC at a target from a first client, beginning execution of a first RPC procedure corresponding to the first RPC, receiving a second RPC at the target from a second client, and completing the execution of the first RPC procedure, and beginning execution of a second RPC procedure corresponding to the second RPC, the first RPC and the second RPC including the same parameter, or processing the first RPC procedure and the second RPC procedure in parallel, the first RPC and the second RPC including different respective parameters.

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 method and system for managing and automating the transactional processes between organizations that do business together using incompatible preexisting transactional systems. A centralized server manages transactions sent and received between the transactional systems of the organizations, and a software implemented messaging application communicates with the centralized server, both transmitting and receiving transactions from and to the transactional system of each organization, the result of which is improved automation of the transactional processes between organizations that do business together using incompatible preexisting transactional systems.

A method including communicatively coupling a wearable device with a companion device, mirroring, by the wearable device, data obtained from a peripheral device of the wearable device on the companion device as peripheral data, including obtaining, by the wearable device, the peripheral data from the peripheral device, and communicating, by the wearable device, the peripheral data to the companion device, receiving, by the companion device, the peripheral data and processing the peripheral data into processed data, sending, by the companion device, the processed data to the wearable device, and receiving, by the wearable device, the processed data and utilizing the processed data to complete a computing process.

Techniques include adding a trusted wearable services module to a sandbox/isolated module on the companion device. e.g., to Private Compute Core. This trusted wearable services module has a secure connection to the camera on the wearable device and prevents other modules on the companion device from viewing the private data. The trusted wearable services has the ability to encrypt and decrypt data from the camera and also performs the processing used to determine user context in an ambient sensing situation.

A stack-based conversation engine is provided. The conversation engine enables a voice or text based virtual assistant to create interactive, conversational experiences in an extensible manner. The conversation engine can be used to support a conversation between a user and a virtual assistant. The conversation engine can be configured to receive, from the virtual assistant, a fulfillment request specifying an intent from the virtual assistant; push an item onto a conversation stack stored, the item including an identifier of the intent; execute an action handler associated with the intent to generate instructions to manipulate the conversation stack; manipulate the conversation stack according to the instructions; and store the conversation stack for subsequent processing in support of the conversation.

A computer system hosting (micro)services that uses a service mesh to govern communication between the services. The services include consumer services and an event stream service, the latter directing an event stream from a producer service to the individual consumer services. The control plane of the service mesh has the role of creating and removing service instances. Based on a specified event capacity that is to be provided by the consumer services collectively, the control plane manages service provisioning by estimating the current event capacity of the system. This is done by measuring the event capacities of each consumer service instance and summing them, from which any shortfall or excess of the current event capacity in relation to the specified event capacity can be determined. Consumer service instances are then added in case of a shortfall or removed in case of an excess as needed to avoid over or under-provisioning.

While displaying a view of a first application of a plurality of applications stored in the memory, an electronic device displays a representation of a first shared content item that upon selection is invoked by the first application, and a selectable attribution affordance that provides a link to a location in a second application where information identifying the first shared content item was initially shared.

A service may be provided that reads sensors, and that communicates information based on the sensor readings to applications. In one example, an operating system provides a sensor interface that allows programs that run on a machine to read the values of sensors (such as an accelerometer, light meter, etc.). A service may use the interface to read the value of sensors, and may receive subscriptions to sensor values from other programs. The service may then generate messages that contain the sensor value, and may provide these messages to programs that have subscribed to the messages. The messages may contain raw sensor data. Or, the messages may contain information that is derived from the sensor data and/or from other data.

Methods and systems for providing data analytics and generating real-time and historical views of network events using a single processing pipeline, managed by a single code base, are presented. A computing device may receive a stream of data indicative of a plurality of events occurring on a network. The computing device may process the stream of data to generate intermediate data and batch data using the single processing pipeline. The intermediate data may be available to generate historical views and the batch data may include a plurality of intermediate data for a time interval. The computing device may generate a historical view of the events based on a subset of intermediate data and the batch data. Finally, the computing device may provide the historical view to a processing layer to enable the computing device to respond to requests for information about the network.