Plug-in document resource control method and client based on middleware plug-in framework

Abstract

A plug-in document resource control method based on a middleware plug-in framework and a client, the method includes: setting the middleware plug-in framework in the client; when a plug-in of the client is started, the plug-in manager verifies the plug-in; when the plug-in When the plug-in passes the verification, the plug-in manager randomly assigns a plug-in instance identifier to the plug-in; during the running of the plug-in, the plug-in framework module in the plug-in unit registers the plug-in instance identifier in the plug-in interface of the plug-in framework module; When the plug-in operates on a file, the plug-in framework module monitors the file operation of the plug-in according to the preset file operation conditions and the plug-in instance identifier of the plug-in; if the file operation of the plug-in meets the preset file operation conditions, control Continue with document operations. Utilizing the middleware plug-in frame created by the invention, a self-defined function plug-in can be quickly developed, and the document resource usage of the plug-in can be controlled.

Description

technical field [0001] The invention relates to a middleware design system and method, in particular to a middleware plug-in frame-based plug-in document resource control method and a client. Background technique [0002] Traditional plug-in development requires a large number of technicians to complete, and the coupling between the developed plug-in and middleware (such as iPanel middleware) is too high, the security is low, and the corresponding underlying equipment cannot be controlled through the plug-in. At the same time, the existing middleware cannot control the plug-in status and resource usage. [0003] Judging from the current development trend, the function extension of middleware is already very complicated and requires a lot of resources to maintain, while the maintenance time of the unique content of middleware itself is relatively short, which seriously affects the quality of all aspects of the product. At the same time, the existing middleware lacks the nece...

AI Technical Summary

Problems solved by technology

[0002] Traditional plug-in development requires a large number of technical personnel to complete, and the coupling between the developed plug-in and middleware (such as iPanel middleware) is too high, and the security is low, so it is impossible to control the corresponding underlying device through the plug-in

At the same time, the existing middleware cannot control the plug-in status and resource usage

[0003] Judging from the current development trend, the function extension of middleware is already very complicated, requiring a lot of resources to maintain, while the maintenance time of the unique content of middleware itself is relatively small, which seriously affects the quality of all aspects of the product

At the same time, the existing middleware lacks the necessary flexibility, and the function scalability is poor, which brings a great burden to the development and maintenance personnel.

[0004] In particular, existing middleware controls document resources only by presetting a large threshold, and plug-in operations are allowed if the threshold is not exceeded. This control method may bring risks to middleware

In addition, the existing middleware only controls document resource management for a fixed application (one instance). When a plug-in is triggered by a page, there may be multiple instances of the same plug-in. The existing middleware cannot Control over multiple instances

Images