Runtime Effective Dater Intercepts Legacy Object Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy applications often lack native support for effective dating of data fields, leading to inefficient implementation and increased computational resources, making it time-consuming and resource-intensive to provide effective dating logic within applications.
Innovation Solution
A method that intercepts access to non-effective date-enabled objects during runtime, redirecting these accesses to effective date-enabled objects to retrieve and maintain sets of values relevant to the access context, thereby enabling effective dating without bloating the object model.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If effective dating logic is implemented within legacy applications, then historical record capability is improved, but implementation time and computational resources increase
Solution Approach 1:
The patent introduces an effective dater component as an intermediary that sits between the application and the database. This mediator intercepts database calls, determines whether effective dating should be applied based on policy rules, and manages the complexity of effective dating logic externally. This allows legacy applications to gain effective dating capability without modifying their core code, thus reducing implementation time while maintaining historical record capability.
Solution Approach 2:
The patent extracts the effective dating logic from the legacy application code and places it in a separate effective dater component. By taking out the complex effective dating implementation details from the application, the patent reduces the time and effort required to implement effective dating within the application, while still providing the desired historical record functionality through the external effective dater.
2Loss of information
If effective dating is applied to data fields, then data traceability is improved, but computational resources and storage overhead increase
Solution Approach 1:
The patent implements partial effective dating by applying effective dating logic only to specific data fields and objects that require it, rather than universally to all data. The effective dater evaluates policy rules to determine which fields need effective dating, thus providing data traceability where needed while avoiding the computational overhead of applying effective dating to all data fields unnecessarily.
Solution Approach 2:
The patent segments the effective dating functionality into discrete policy rules that can be independently evaluated. The effective dater processes database calls by evaluating applicable policies one at a time, allowing for efficient computational resource usage. This segmented approach to policy evaluation reduces the overall computational burden compared to a monolithic effective dating implementation.
3Loss of information
If effective dating logic is integrated into legacy applications, then historical data access is improved, but object model complexity increases
Solution Approach 1:
The effective dater acts as an intermediary layer between the legacy application and the database, handling all effective dating logic externally. This mediator approach allows historical data access to be improved without increasing the complexity of the application's object model, as the effective dating functionality is encapsulated in a separate component that the application interacts with through simple database call interception.
Data Source
AI summary
An effective dater provides effective dating to object in a runtime environment. The effective dater identifies an access to a first field of a first object during runtime of a program. The first object is not effective date enabled. The effective date of determines whether the effective dating is to be applied to the first field. In response to determining that effective dating is to be applied to the first field, the effective dater redirects the access to a second object. The second object is effective date enabled. The effective dater then accesses the effective dated value in the second field of the second object according to an access context.