Remote Event Bridge for Bi-directional Object Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional remoting techniques in object-oriented programming are limited in accessing and efficiently managing features of remote objects, particularly in web applications like Rich Internet Applications (RIAs), where they often require modifications to remote objects and are uni-directional, lacking flexibility and efficiency.

Innovation Solution

The implementation of a remote event bridge that allows observer objects to subscribe to and communicate with subject objects without modifying them, enabling bi-directional communication and anonymous subscription/unsubscription, using a publish/subscribe model with a surrogate object to handle event notifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional remoting techniques are used to access remote object features, then data can be passed to remote objects for processing, but the techniques are limited in accessing events and require modifications to remote objects

Engineering Contradiction:
Improveaccess to remote object eventsVSAvoidmodifications to remote objects
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an event bridge as an intermediary component that sits between the local observer object and the remote subject object. This event bridge handles event subscriptions and notifications, allowing the local object to access remote object events without modifying the remote object itself. The event bridge translates and forwards events across process boundaries, resolving the contradiction between event accessibility and object integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If conventional remoting techniques are used, then remote object access is possible, but communication is uni-directional and lacks flexibility

Engineering Contradiction:
Improvecommunication flexibilityVSAvoidremoting configuration
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The event bridge is designed as a universal component that handles multiple communication patterns including event subscriptions, notifications, and method invocations. It supports both push and pull communication models, enabling flexible bi-directional interaction between local and remote objects. This multi-functional design improves ease of operation by providing a unified interface for various communication needs while managing complexity internally.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If remote objects are modified to enable event access, then event communication is possible, but the original programming of legacy objects must be changed

Engineering Contradiction:
Improveevent subscription capabilityVSAvoidsoftware modification effort
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system segments the event communication functionality into a separate event bridge component rather than integrating it directly into the remote objects. This segmentation allows legacy objects to remain unchanged while the event bridge handles all event-related operations. The event bridge maintains event handlers and subscriptions independently, enabling event access without modifying the original object code or structure.

Inventive Principle:
Principle #1Segmentation

4Productivity

If conventional remoting is used in RIAs, then web application functionality is achieved, but server configuration requirements increase

Engineering Contradiction:
ImproveRIA functionalityVSAvoidserver configuration
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The event bridge implements self-service mechanisms by automatically managing event subscriptions, notifications, and routing without requiring extensive server configuration. It handles event lifecycle management, including registration, delivery, and unsubscription, autonomously. This reduces the burden on server configuration while maintaining full RIA functionality, as the event bridge adapts to different scenarios without manual intervention.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10318359B2Techniques to remotely access object events
Publication Date: 2019.06.11 SAS INSTITUTE INC
  • US10318359B2 patent drawing
  • US10318359B2 patent drawing
  • US10318359B2 patent drawing

AI summary

Various embodiments are generally directed to techniques to remotely access object events. An apparatus may comprise a processor and a memory communicatively coupled to the processor. The memory may be operative to store a remote event bridge having a surrogate object that when executed by the processor is operative to allow an observer object for a first process to subscribe to an event of a subject object for a second process using the surrogate object. In this manner, the remote event bridge and the surrogate object operates as an interface between subject objects and observer objects without any modifications to either class of objects.