Dynamic Link Handler Generation via URI Reflection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing link request processing methods through hardcoding are complicated and require frequent adjustments to coupling files for newly added services, making them inflexible and inconvenient.
Innovation Solution
A method and apparatus that generate a link handler based on service module parameters and action parameters, allowing for page jumping without the need to readjust coupling files, using a reflection interface and configuration files to determine the corresponding link handler and perform page navigation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If hardcoding is used to process link requests, then the link request can be processed with predetermined coupling files, but the processing procedure becomes complicated and requires frequent adjustments for newly added services
Solution Approach 1:
The patent extracts the service module identifier from the link request URI and uses it to directly determine the target service module, eliminating the need to query predetermined coupling files. This extraction approach simplifies the processing procedure while maintaining reliable link request handling.
Solution Approach 2:
The patent introduces a reflection interface as an intermediary mechanism that enables dynamic determination of service modules based on their identifiers in the URI. This reflection interface acts as a mediator between the link request and the service module selection, eliminating the need for hardcoding and coupling file queries.
2Adaptability or versatility
If hardcoding is used to process link requests, then the coupling file can be used to determine service modules, but the coupling file needs to be readjusted for newly added services
Solution Approach 1:
The patent transforms the static coupling file-based service module determination into a dynamic mechanism where service modules are automatically discovered through their identifiers in the URI. This dynamic approach allows new services to be added without modifying the coupling file, significantly improving adaptability.
Solution Approach 2:
The patent enables service modules to self-identify through their identifiers embedded in the URI. The reflection interface automatically resolves these identifiers to the corresponding service modules, eliminating the need for manual coupling file adjustments when new services are added.
3Ease of operation
If hardcoding is used to process link requests, then the link handler can be generated based on header files, but the overall processing procedure becomes complicated
Solution Approach 1:
The patent extracts the service module identifier directly from the URI and uses it to determine the link handler, eliminating the need to query header files through complex procedures. This extraction simplifies the overall processing workflow while maintaining ease of operation.
Solution Approach 2:
The reflection interface serves as an intermediary that simplifies the connection between URI identifiers and link handlers. It automatically resolves the identifier to the appropriate handler without requiring complex header file queries, making the process easier to operate.
Data Source
AI summary
A link request for a service is received. The link request includes an action parameter associated with an action that is to be executed in response to the link request. A determination is made as to whether the link request includes a service module identifier associated with a service provider that provides the service. In response to determining that the link request includes the service module identifier, a target page is determined and a link handler is generated. The target page is determined based on the service module identifier and the action parameter. The link handler is generated based on the service module identifier and the action parameter. The link handler is configured, when executed, to retrieve the target page. The link handler is executed based on the action parameter to retrieve the target page.