Abstract: A display control device includes a sift portion that sifts a transition request event stored in a queue. The sift portion monitors the queue. When the queue stores several transition request events corresponding to the same type of screen-image after transition, the sift portion retains the most recent one of the transition request events and discards the other transition request events corresponding to the same type of screen-image after transition. This can decrease transition request events stored in the queue compared to a case of not sifting transition request events and reduce a possibility of generating a delay. The sift portion does not sift a transition request event that transitions to a different type of screen-image. This can display the type of screen-image a user intends to display based on his or her manipulation.

Abstract: Modal dynamic analysis for finite element models (FEMs) that include Lagrange multipliers may generate incorrect stress and reaction forces. Computer systems and computer-implemented methods are provided for modifying the modal analysis to correctly generate stress and reaction forces. The systems and methods perform the modal analysis by employing a FEM and modeling stress and reaction forces of the FEM using Lagrange multipliers. The systems and methods calculate a correction term that comprises corrected values of the Lagrange multipliers. The methods and systems modify (and improve) the modal analysis by using the correction term to correct the Lagrange multipliers of the FEM, which enables the modal analysis to generate correct stress and reaction forces.

Abstract: Aspects of the present invention provide a memory system comprising a plurality of stacked memory layers, each memory layer divided into memory sections, wherein each memory section connects to a neighboring memory section in an adjacent memory layer, and a logic layer stacked among the plurality of memory layers, the logic layer divided into logic sections, each logic section including a memory processing core, wherein each logic section connects to a neighboring memory section in an adjacent memory layer to form a memory vault of connected logic and memory sections, and wherein each logic section is configured to communicate directly or indirectly with a host processor. Accordingly, each memory processing core may be configured to respond to a procedure call from the host processor by processing data stored in its respective memory vault and providing a result to the host processor. As a result, increased performance may be provided.

Abstract: An event clearinghouse engine is used with a data storage system to modify event disposition associated with components. A separate component disposition table is provided for each component. The component disposition table specifies different sets of disposition modifications for different types of events as indicated by event ID. A global disposition rule mapping table includes disposition modifications which are applied to all events. Per-vendor and per-tenant tables may be used to specify disposition modifications for particular vendors and tenants. Mode-specific tables such as a rescue/recovery mode table may be used to specify disposition modifications when the storage system is in a particular mode. The tables may be implemented in stages, including parallel and serial application.

Abstract: A method for controlling the interoperation of a plurality of software applications and resources includes intercepting communications from a first application to a second application or resource, directing the communication to a context management system, generating a candidate list of contexts for the communication, evaluating the candidate list according to at least one policy defined for these contexts to identify the resultant action and namespace for the communication, and performing the action as defined by the policies within the identified namespace. The method further includes tracking one or more versions of the second application, as well as tracking an evolution of application and/or resource names. The method further includes identifying one or more operations associated with a context on the candidate list, and executing the identified operations prior to a further communication.

Abstract: A system is provided for an application executed by a client to invoke a remote object method of a remote object of a remote object class that is hosted by a server. The application instantiates a proxy of a proxy class that includes a proxy member function with the same signature as the remote object member function. The application associates an object identifier with the proxy. The application invokes the proxy member function of the proxy. Under control of the invoked proxy member function, the application sends to the server an invocation request message that includes the object identifier that is associated with the proxy and an identifier of the remote object member function. The application relies on functionality provided by the browser without the need for the browser to access add-on functionality when executing the application.

Abstract: Embodiments of the disclosure provide high-level primitives that facilitate communication between a user-space application and an operating system kernel. Transport components reside in user-space and in kernel-space that, upon either the application or a kernel module requesting to invoke a callback, deliver parameters and other data back and forth to one another, allowing the user-space application and kernel module to communicate as if directly invoking the callback. Embodiments also provide for a definition standard that third-party developers can use to automatically emit a header file and macros for sending events and dispatching callbacks.

Abstract: A consumer transmits a set of system updates corresponding to an initial set of events retrieved from an event stream. The consumer determines that acknowledgement of the transmission of the initial set of events has not been received. The consumer executes another retrieval operation to retrieve events from the event stream which results in retrieving an updated set of events. The updated set of events includes the initial set of events and one or more additional events. The consumer trims the updated set of events to remove the one or more additional events and obtains the initial set of events. The consumer re-determines and re-transmits the system updates corresponding to the initial set of events that were obtained by trimming the updated set of events.

Abstract: Processor based systems and methods of defining a scenario event comprising the steps of identifying an event having an event attribute and generalizing the event attribute to define a generalized event whereby the generalized event is the scenario event. In some embodiments, the steps further comprise identifying a first and second event, generalizing a first and second event attribute to define a first and second generalized event and connecting the first and second generalized event in a continuous envelope to create a scenario envelope. Processor based systems and methods of monitoring an activity comprising the steps of monitoring an activity having an activity attribute and comparing the activity attribute to an event envelope to determine a status of the activity relative to the event envelope.

Abstract: Systems, methods, and computer-readable media are disclosed for identifying duplicate events. In one implementation, a computer-implemented method is provided that includes receiving an event based on a user interaction with a client device, and determining content and a location for the event. The method further includes calculating a duplicate value for the event using the content and the location of the even, and determining a degree of similarity by comparing the duplicate value to a table of stored duplicate values. In addition, the method includes identifying the event as a duplicate of a stored event when the degree of similarity exceeds a predetermined threshold level of similarity, and indexing the event on the client device depending on the determination of whether or not the event is a duplicate of the stored event.

Abstract: A digital assistant includes an extensibility client that interfaces with application extensions that are built by third-party developers so that various aspects of application user experiences, content, or features may be integrated into the digital assistant and rendered as native digital assistant experiences. Application extensions can use a variety of services provided from cloud-based and/or local sources such as language/vocabulary, user preferences, and context services that add intelligence and contextual relevance while enabling the extensions to plug in and operate seamlessly within the digital assistant context. Application extensions may also access and utilize general digital assistant functions, data structures, and libraries exposed by the services and implement application domain-specific context and behaviors using the programming features captured in the extension.

Abstract: Systems and methodologies for accessing resources associated with a Web-based application in accordance with one or more embodiments disclosed herein may include a browser that obtains at least first resources from a first domain and second resources from a second domain and a resource management component that facilitates controlled communication between the first resources and the second resources and prevents the first resources and the second resources from accessing other resources that the first resources and the second resources are not permitted to access. The resource management component may be further operable to contain restricted services in a sandbox containment structure and/or to isolate access-controlled resources in a service instance. In addition, the resource management component may be operable to facilitate the flexible display of resources from disparate domains and/or controlled communication therebetween.

Abstract: A system includes information for generating a first appliance based on first appliance information, information for generating a second appliance based on second appliance information, and information for configuring communication between the first appliance and the second appliance. The system further includes at least one processor configured to generate a first volume by copying the first appliance information using a first set of parameters associated with an environment in which the first volume is situated, and generate a second volume by copying the second appliance information using a second set of parameters associated with an environment in which the second volume is situated. The system also includes at least one processor configured to initiate a first appliance instance by executing code from the first volume using information in the third volume, and initiate a second appliance instance by executing code in the second volume using information in a fourth volume.

Abstract: Methods and systems are provided for Remote Application Programming Interface (RAPI) communications between server and client devices. In an embodiment, server and client devices comprise memories and hardware processors coupled to the memories. The hardware processors execute instructions to perform operations that instantiate access point instances on both server side and client side. The instructions are generated from compiling API interface classes with remote communication classes, wherein the compiling includes a procedure of creating new classes through double inheritance. By receiving an API connection message from a client device, the server device clones a default relayer access point instance and assigns the cloned relayer access point instance to process API requests received thereafter from the client device.

Abstract: Various embodiments are generally directed to an apparatus, method and other techniques for receiving information to invoke a transition from a first operating system to a second operating system, copying a system context for the second operating system from a location of a non-volatile memory to a volatile memory, the location associated with the second operating system and transitioning from the first operating system to the second operating system using the system context for the second operating system.

Abstract: A parallel execution runtime prevents stack overflow by maintaining an inline counter for each thread executing tasks of a process. Each time that the runtime determines that inline execution of a task is desired on a thread, the runtime determines whether the inline counter for the corresponding thread indicates that stack overflow may occur. If not, the runtime increments the inline counter for the thread and allows the task to be executed inline. If the inline counter indicates a risk of stack overflow, then the runtime performs additional one or more checks using a previous stack pointer of the stack (i.e., a lowest known safe watermark), the current stack pointer, and memory boundaries of the stack. If the risk of stack overflow remains after all checks have been performed, the runtime prevents inline execution of the task.

Abstract: In a transactional memory environment including a first processor and one or more additional processors, a computer-implemented method includes, by the first processor, initializing a time record, listening for zero or more probes from the one more additional processors, responding to each probe of the zero or more probes, and logging each probe of the zero or more probes to yield a probe log. The computer-implemented method further includes, by the first processor, receiving a probe report directive and, responsive to the probe report directive, generating a probe report indication based on the probe log. The probe report indication denotes whether, since the time record, the first processor has received any of the zero or more probes. The computer-implemented method further includes ending the time record. A corresponding computer program product and computer system are also disclosed.

Abstract: In a transactional memory environment including a first processor and one or more additional processors, a computer-implemented method includes, by the first processor, initializing a time record, listening for zero or more probes from the one more additional processors, responding to each probe of the zero or more probes, and logging each probe of the zero or more probes to yield a probe log. The computer-implemented method further includes, by the first processor, receiving a probe report directive and, responsive to the probe report directive, generating a probe report indication based on the probe log. The probe report indication denotes whether, since the time record, the first processor has received any of the zero or more probes. The computer-implemented method further includes ending the time record. A corresponding computer program product and computer system are also disclosed.

Abstract: Provided is a system and method for interface call, relating to the enterprise management technology field. The system includes: an interface management component which is configured to generate a description file and a call process indication of an interface according to an interface modification requirement of a user, and deploy the description file and the call process indication to an interface execution component, wherein the description file includes configuration replacement information of the interface; and the interface execution component, which is configured to configure the interface according to the description file, and call the interface according to the call process indication.

Abstract: Architecture that includes an asynchronous library which remembers the synchronization context that initiated an asynchronous method call and when the request is completed, the library restores the synchronization context of the calling thread before executing a callback. This ensures that the callback executes on the same thread as the original asynchronous request. The callback to the asynchronous operation that asynchronous library provides automatically “jumps threads” to maintain thread affinity.