A non-intrusive interface software system interface implementation method
By managing the dependencies of C/S architecture programs through non-intrusive API middleware, the problem of closed API interfaces in C/S architecture programs is solved, enabling stable and fast data interaction and independent evolution, and reducing system coupling and integration complexity.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- GUIZHOU HONGLIN MACHINERY
- Filing Date
- 2023-08-24
- Publication Date
- 2026-07-03
AI Technical Summary
The closed API interface of existing C/S architecture programs makes it impossible to interact with other systems. Intrusive interface methods will break the original logic code and become unusable after system updates, making it difficult to achieve stable and flexible data interaction.
By defining middleware constructors and interface methods to add injection points, a non-intrusive API middleware is implemented to manage system dependencies, provide interface injection methods and parameters, and introduce non-intrusive API middleware as a bridge to reduce coupling and achieve decoupling.
Protect the stability and integrity of existing software, avoid direct modification of source code, reduce risks, enable rapid integration and expansion, achieve independent evolution of software and external systems, and provide flexible integration methods.
Smart Images
Figure CN117234625B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of system interface technology, and in particular to a non-intrusive interface software system interface implementation method. Background Technology
[0002] C / S architecture programs have their own closed nature. Generally, vendors do not provide API interfaces for C / S software architecture programs. In this case, it is impossible to interact with other systems. Using intrusive interface methods, such as accessing DLL files and extending based on DLL files, will destroy the original logic code and cause permanent damage to the system. Moreover, after the system is updated and upgraded, the original intrusive code will be overwritten again, making the interface unusable and making it difficult to achieve good usage results. Summary of the Invention
[0003] The purpose of this invention is to solve the technical problems mentioned in the background section.
[0004] This invention adopts the following technical solution: a non-intrusive interface software system interface implementation method, comprising the following steps:
[0005] S1: Implement non-intrusive API middleware by defining a middleware constructor or adding injection points to the interface methods of an object;
[0006] S2: By delegating the management of dependencies between systems to middleware, a non-intrusive API middleware interface is implemented, reducing the coupling between systems and improving the flexibility and testability of the code;
[0007] S3: Provides interface injection methods and parameters through non-intrusive API middleware, and removes the system object dependencies from the system itself, allowing external systems to be responsible for creating and injecting dependencies;
[0008] S4: Integrate or extend existing software with non-intrusive API middleware, providing a bridge for interaction with external systems without requiring large-scale modifications and redeployment of existing software.
[0009] S5: Introduce non-intrusive API middleware between existing software and external systems to decouple them, allowing the software and external systems to evolve independently without affecting each other.
[0010] Preferably, when implementing non-intrusive API middleware by defining a middleware constructor in S1, dependency parameters need to be declared in the object's constructor. This is to enable automatic resolution of the non-intrusive API middleware when the object is created.
[0011] Preferably, in step S1, when implementing a non-intrusive API middleware by adding injection points to the interface methods of an object, the middleware needs to call the interface methods after creating the object to inject dependencies into the interface system. This ensures that dependencies can be injected into the system correctly.
[0012] Preferably, in step S1, a suitable middleware interface is selected based on specific project requirements and development environment to implement a non-intrusive API middleware. This ensures that the non-intrusive API middleware can adapt to specific project needs and development environment, achieving better performance.
[0013] Preferably, the dependencies in S3 can be other objects, services, configuration data, etc. Here, dependency means that an object needs another object or external resource to complete its function, and an object may have one or more dependencies.
[0014] Preferably, in S3, interface injection refers to the injection of dependencies through interface methods implemented by the object. After the object is created, the container calls the interface method, passing the dependency as a parameter, to complete the dependency injection. This ensures that the dependency injection proceeds correctly.
[0015] Preferably, in step S4, integrating or extending existing software with non-intrusive API middleware enables rapid development and deployment while reducing the complexity of integration and extension. This allows for rapid development and deployment while minimizing the complexity of integration and extension, ensuring smooth integration and extension processes.
[0016] Preferably, in S5, decoupling refers to the reduction of coupling between objects by inversion of control, allowing objects to focus only on their own responsibilities without needing to worry about the creation and management of dependent objects. Here, decoupling is achieved between existing software and external systems, enabling the software and external systems to evolve independently without affecting each other.
[0017] Preferably, in step S5, after introducing a non-intrusive API middleware between the existing software and the external system, the existing software and the external system can evolve independently. Here, the non-intrusive API middleware is designed so that it does not affect the software and the external system, allowing them to evolve and improve independently.
[0018] Preferably, in step S5, when it is necessary to change the implementation of an external system or add a new external system, the middleware can provide a more flexible integration method without directly affecting the existing software. This allows the software to be developed normally, integrating the middleware in a more flexible manner.
[0019] Compared with the prior art, the advantages and positive effects of the present invention are as follows:
[0020] In this invention, data interaction is achieved through a non-intrusive API middleware, protecting the stability and integrity of existing software. This avoids directly modifying the source code of existing software, thus protecting its stability and integrity, reducing the risks that direct source code modification might introduce, preventing the introduction of new errors or damage to existing functions. Furthermore, using non-intrusive API middleware allows for faster integration and extension of existing software. The middleware provides a bridge for interaction with external systems without requiring large-scale modifications and redeployment of existing software, thereby accelerating development and deployment, and reducing the complexity of integration and extension. Simultaneously, by introducing a middleware layer, existing software can be decoupled from external systems, allowing them to evolve independently without affecting each other. When changes to the implementation of external systems or the addition of new external systems are needed, the middleware provides a more flexible integration method without directly impacting existing software, achieving better usability. Attached Figure Description
[0021] Figure 1 This invention presents a structural schematic diagram of a non-intrusive interface software system interface implementation method. Detailed Implementation
[0022] To better understand the above-mentioned objectives, features, and advantages of the present invention, the present invention will be further described below in conjunction with the accompanying drawings and embodiments. It should be noted that, unless otherwise specified, the embodiments and features described in these embodiments can be combined with each other.
[0023] Numerous specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways than those described herein, and therefore the invention is not limited to the specific embodiments disclosed in the following specification.
[0024] Example
[0025] Please see Figure 1 This invention provides a technical solution: a method for implementing an interface in a non-intrusive interface software system, comprising the following steps:
[0026] S1: Implement non-intrusive API middleware by defining a middleware constructor or adding injection points to the interface methods of an object;
[0027] S2: By delegating the management of dependencies between systems to middleware, a non-intrusive API middleware interface is implemented, reducing the coupling between systems and improving the flexibility and testability of the code;
[0028] S3: Provides interface injection methods and parameters through non-intrusive API middleware, and removes the system object dependencies from the system itself, allowing external systems to be responsible for creating and injecting dependencies;
[0029] S4: Integrate or extend existing software with non-intrusive API middleware, providing a bridge for interaction with external systems without requiring large-scale modifications and redeployment of existing software.
[0030] S5: Introduce a non-intrusive API middleware between existing software and external systems to decouple them, allowing the software and external systems to evolve independently without affecting each other.
[0031] Please see Figure 1In S1, when implementing non-intrusive API middleware by defining a middleware constructor, dependency parameters need to be declared in the object's constructor so that the non-intrusive API middleware can automatically resolve them when the object is created. In S1, when implementing non-intrusive API middleware by adding injection points to the object's interface methods, the middleware needs to call the interface methods after object creation to inject dependencies into the interface system, ensuring proper dependency injection. In S1, it's necessary to select a suitable middleware interface based on specific project requirements and development environment to implement non-intrusive API middleware, ensuring it adapts to specific project needs and development environments for better performance. In S3, dependencies can be other objects, services, configuration data, etc. A dependency means that an object needs another object or external resource to complete its function, and an object may have one or more dependencies. In S3, interface injection means that dependencies are injected through the interface methods implemented by the object. After object creation, the container calls the interface methods and passes the dependencies as parameters to complete the dependency injection, ensuring proper dependency injection. In S4, integrating or extending existing software with non-intrusive API middleware accelerates development and deployment, reducing integration and extension complexity. In S5, decoupling refers to Inversion of Control reducing coupling between objects, allowing them to focus on their own responsibilities without worrying about the creation and management of dependent objects. This decoupling enables existing software to evolve independently without affecting external systems. Furthermore, the introduction of non-intrusive API middleware between existing software and external systems in S5 allows for independent evolution without impacting the software or external systems. When changes to external system implementations or the addition of new external systems are needed, the middleware provides more flexible integration methods without directly affecting existing software, enabling normal software development and more flexible middleware integration.
[0032] Working principle: Data interaction is achieved through non-intrusive API middleware, protecting the stability and integrity of existing software. This avoids directly modifying the source code of existing software, thus protecting its stability and integrity, reducing the risks that may be introduced by direct source code modification, preventing the introduction of new errors or damage to existing functions. Furthermore, using non-intrusive API middleware allows for faster integration and extension of existing software. The middleware provides a bridge for interaction with external systems without requiring large-scale modifications and redeployment of existing software, thereby accelerating development and deployment speed and reducing the complexity of integration and extension. Simultaneously, by introducing a middleware layer, existing software can be decoupled from external systems, allowing them to evolve independently without affecting each other. When changes to the implementation of external systems or the addition of new external systems are needed, the middleware provides a more flexible integration method without directly impacting existing software, achieving better usability.
[0033] The above are merely preferred embodiments of the present invention and are not intended to limit the present invention in any other way. Any person skilled in the art may make changes or modifications to the above-disclosed technical content to create equivalent embodiments that can be applied to other fields. However, any simple modifications, equivalent changes, and modifications made to the above embodiments based on the technical essence of the present invention without departing from the scope of the present invention shall still fall within the protection scope of the present invention.
Claims
1. A method for implementing an interface in a non-intrusive interface software system, characterized in that, Includes the following steps: S1: Implement non-intrusive API middleware by defining a middleware constructor or adding injection points to the interface methods of an object; S2: By delegating the management of dependencies between systems to middleware, a non-intrusive API middleware interface is implemented, reducing the coupling between systems and improving the flexibility and testability of the code; S3: Provides interface injection methods and parameters through non-intrusive API middleware, and removes the system object dependencies from the system itself, allowing external systems to be responsible for creating and injecting dependencies; S4: Integrate or extend existing software with non-intrusive API middleware, providing a bridge for interaction with external systems without requiring large-scale modifications and redeployment of existing software. S5: Introduce non-intrusive API middleware between existing software and external systems to decouple them, allowing the software and external systems to evolve independently without affecting each other.
2. The non-intrusive interface software system interface implementation method according to claim 1, characterized in that: When implementing a non-intrusive API middleware by defining a middleware constructor in S1, dependency parameters need to be declared in the object's constructor.
3. The non-intrusive interface software system interface implementation method according to claim 1, characterized in that: In S1, when implementing a non-intrusive API middleware by adding injection points to the interface methods of an object, the middleware needs to call the interface methods to inject dependencies into the interface system after the object is created.
4. The non-intrusive interface software system interface implementation method according to claim 1, characterized in that: In S1, a suitable middleware interface needs to be selected based on specific project requirements and development environment to implement a non-intrusive API middleware.
5. The non-intrusive interface software system interface implementation method according to claim 1, characterized in that: In S3, dependencies can be other objects, services, or configuration data.
6. The non-intrusive interface software system interface implementation method according to claim 1, characterized in that: In S3, interface injection refers to the injection of dependencies through interface methods implemented by objects. After an object is created, the container calls the interface method and passes the dependency as a parameter to complete the dependency injection.
7. The non-intrusive interface software system interface implementation method according to claim 1, characterized in that: By integrating or extending existing software with non-intrusive API middleware in S4, development and deployment speed can be increased rapidly, while reducing the complexity of integration and extension.
8. The non-intrusive interface software system interface implementation method according to claim 1, characterized in that: In S5, decoupling means that inversion of control reduces the coupling between objects, allowing objects to focus only on their own responsibilities without having to worry about the creation and management of dependent objects.
9. The non-intrusive interface software system interface implementation method according to claim 1, characterized in that: In S5, after introducing a non-intrusive API middleware between existing software and external systems, the existing software and external systems can evolve independently.
10. The non-intrusive interface software system interface implementation method according to claim 1, characterized in that: In S5, when it is necessary to change the implementation of an external system or add a new external system, the middleware can provide a more flexible integration method without directly affecting the existing software.