Backing Files for Portal Element Control Interaction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing portal technologies lack a structured mechanism for developers to interact with portal element controls without directly exposing them, which limits the ability to update and improve portal applications without affecting existing implementations.
Innovation Solution
The introduction of backing files and backing contexts allows developers to interact with portal element controls through lifecycle methods, enabling them to run business logic, modify displays, and manage events before rendering, while maintaining thread safety and hiding certain control methods from direct exposure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If portal element controls are directly exposed to developers, then developers can freely interact with controls and implement custom logic, but it becomes difficult to update and improve portal applications without affecting existing implementations
Solution Approach 1:
The patent introduces backing files as an intermediary layer between developers and portal element controls. These backing files contain controller code that mediates all interactions with the controls, allowing developers to work with stable, well-defined interfaces while the actual control implementation can be updated independently. The backing context serves as another intermediary, providing a controlled access mechanism to control state and events.
Solution Approach 2:
The patent segments the portal application into distinct components: portal element controls, backing files with controller code, and backing contexts. This segmentation allows each component to be developed, updated, and maintained independently. The controls can be improved without affecting developers who only interact through the stable backing file interfaces.
2Productivity
If portal element controls are updated and improved, then functionality and performance can be enhanced, but existing implementations may be affected or broken
Solution Approach 1:
Backing files serve as a stable intermediary layer that shields existing implementations from control updates. Developers write business logic in backing files that interact with controls through defined interfaces. When controls are updated, the backing files remain unchanged, ensuring existing implementations continue to work reliably while benefiting from improved control functionality.
Solution Approach 2:
The patent establishes backing files and backing contexts in advance to create a stable development framework. This preliminary structure defines how developers will interact with controls, so when controls are updated later, the pre-established backing files already provide the necessary abstraction and protection for existing implementations.
3Ease of operation
If all control methods are exposed to developers, then developers have full access to control functionality, but certain control methods should be hidden from direct exposure
Solution Approach 1:
The patent extracts the necessary control interaction capabilities into backing files, separating them from the full control interface. Developers only get access to the specific methods and events they need through the backing context, while other control methods remain hidden. This extraction simplifies the developer-facing interface while maintaining full control functionality behind the scenes.
Solution Approach 2:
The backing context acts as an intermediary that selectively exposes control functionality to developers. It provides access to necessary state information and event management capabilities while filtering out internal control methods that should not be directly accessible. This mediation maintains ease of operation for necessary functions while preventing unnecessary complexity from exposed internal methods.
Data Source
AI summary
Backing files and backing contexts can be associated with portal elements controls for the construction of a portal. The backing files and backing contexts can allow interactions with the portal element controls before rendering. In one embodiment, developers are allowed to have access to backing files and backing contexts. The backing files allows developer code to be run before rendering. The backing contexts allow the setting and getting of information from the portal element controls.