Disclosure of Invention
In order to solve the technical problem that in the prior art, because the starting of the plugin depends on an IE browser, compatibility problems such as different browser versions and plugin required versions or host operating environments and the like possibly occur, so that equipment cannot be used normally, the application provides a localized plugin service method, a localized plugin service device, electronic equipment and a storage medium.
In a first aspect, an embodiment of the present application provides a localized plug-in service method, applied to a host, where the method includes:
receiving a call plug-in request input by a target object;
Determining a light service plug-in to be called according to the call plug-in request;
If the light service plug-in is found in the local plug-in library, acquiring operation environment information, and judging whether the light service plug-in is available according to the operation environment information;
If the light service plug-in is determined to be available, the light service plug-in is packaged into a light service for use by the target object.
Optionally, the operation environment information comprises plug-in dependency relationship, validity period and/or plug-in information of the light service plug-in, and the step of judging whether the light service plug-in is available according to the operation environment information comprises the following steps:
determining a target plugin on which the light service plugin depends according to the dependency relationship, and judging whether the target plugin is stored in the local plugin library;
if the target plugin is stored in the local plugin library, judging whether the validity period of the light service plugin is positioned after the current moment and/or judging whether the plugin information is consistent with preset reference information.
Optionally, the method further comprises:
Determining a plurality of running objects on which the light service plug-in depends according to the running environment information;
Determining a target plug-in for generating the operation objects aiming at each operation object which is not found in the operation objects, and judging whether a device identifier corresponding to the target plug-in is positioned in a permission list;
And if the equipment identifier corresponding to the target plug-in is positioned in the permission list, operating the target plug-in to acquire the operation object generated by the target plug-in.
Optionally, before the step of receiving the call plug-in request entered by the target object, the method further includes:
Acquiring device identifiers of a plurality of devices connected with the host;
According to the operation of selecting the equipment identifier by the target object, determining equipment to be controlled;
If the equipment identifier of the equipment to be controlled is positioned in the permission list, generating a plug-in calling request according to the equipment identifier of the equipment to be controlled;
or if the equipment identifier of the equipment to be controlled is not located in the permission list, acquiring configuration information of the equipment to be controlled;
And if the configuration information meets the preset registration condition, writing the equipment identifier of the equipment to be controlled into the permission list.
Optionally, the creating process of the local plugin library includes:
Acquiring plug-in information of a plurality of light service plug-ins and each light service plug-in;
Determining an operation object and an access address which are depended by the light service plug-in according to the plug-in information and configuration information;
Carrying out security verification on the configuration information;
If the configuration information passes the security verification, the operation object is found in the local plug-in library;
if the running object is not found in the local plug-in library, acquiring the running object from a preset information library and storing the running object into the local plug-in library;
And storing the light service plug-in the local plug-in library, and generating a calling interface of the light service plug-in according to the access address.
Optionally, the method further comprises:
determining equipment identification, authorization information and dependent plug-in information according to the configuration information;
judging whether the equipment identifier is positioned in a permission list or not;
if the equipment identifier is located in the permission list, judging whether the authorization information accords with a preset authorization condition;
If the authorization information accords with a preset authorization condition, determining a dependent plug-in according to the dependent plug-in information, and if the dependent plug-in is located in the local plug-in library, determining that the configuration information passes the security check.
Optionally, the method further comprises:
traversing a plurality of the light services in the host side;
When it is determined that the light service fails, re-performing the step of encapsulating the light service plug-in as a light service to restart the light service;
when the light service is determined to be online, updating and detecting the light service;
and if the light service plug-in is determined to be updated, acquiring an installation piece corresponding to the light service plug-in from an update database, and updating the light service by utilizing the installation piece.
In a second aspect, an embodiment of the present application provides a localized plugin service device, including:
the receiving module is used for receiving a call plug-in request input by the target object;
the determining module is used for determining the light service plugin to be called according to the call plugin request;
The judging module is used for acquiring the operation environment information if the light service plug-in is found in the local plug-in library, and judging whether the light service plug-in is available according to the operation environment information;
And the packaging module is used for calling the light service plug-in to package the light service plug-in into light service for the target object to use if the light service plug-in is determined to be available.
In a third aspect, the present application provides an electronic device comprising a memory, a processor, the memory having stored therein a computer program executable on the processor, the processor implementing the steps of the method of any of the first aspects described above when the computer program is executed.
In a fourth aspect, a computer readable medium having non-volatile program code executable by a processor, the program code causing the processor to perform the method of any of the first aspects.
Compared with the prior art, the technical scheme provided by the embodiment of the application has the advantages that the method and the device have the advantages that through receiving the call plug-in request input by the target object, determining the light service plug-in to be called according to the call plug-in request, acquiring the operation environment information if the light service plug-in is found in the local plug-in library, judging whether the light service plug-in is available according to the operation environment information, calling the light service plug-in to package the light service plug-in into the light service if the light service plug-in is determined to be available, so that the target object can use the request, collision between the plug-in and the three-party software operation environment can be avoided through acquiring the plug-in locally, the availability of the call plug-in can be further ensured by combining the operation environment information, and the effect of high-cohesive coupling and low-cohesive coupling can be realized even if the plug-in faces one-to-many scenes.
DETAILED DESCRIPTION OF EMBODIMENT (S) OF INVENTION
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Currently, with the development of internet technology, cloud services gradually form a new scale trend in combination with edge computing, and in the aspect of centralized processing of cloud computing, a front end puts forward higher requirements on convenience and instant operation response, and meanwhile, the network environment and the local PC are complex and changeable, so that higher requirements are put forward on the security of a desktop end. In order to meet the development of a high-real-time low-delay software system, improve the response timeliness and the system stability of the system, and improve the operation and use safety of a local end at the same time, at present, most of the system uses a plug-in integrated management mode to meet the service requirements of users, for example, in an actual application scene, a desk client is generally connected with various external devices (an identity card reading device, a handwriting screen device, a high-speed image device, a scanning device, a fingerprint recording device and the like), at present, a manufacturer of the external devices provides a calling device plug-in (a dynamic library dll file), a developer performs secondary development, invokes a device plug-in provided by the manufacturer to generate an Activex control, and a user accesses the plug-in (Activex control) obtained by secondary development through an IE browser to call the device, thereby realizing the acquisition of user information. However, in the process of calling the external device, since the plug-in is started depending on the IE browser, compatibility problems such as different browser versions and plug-in requirement versions or host operating environments may occur, so that the device cannot be used normally.
Step S101, receiving a call plug-in request input by a target object;
in this step, the target object may be an administrator at the host side or an object of a business service, which is specifically determined according to the actual situation, and the embodiment of the present application is not limited in this particular way.
In the embodiment of the application, the call plug-in request is determined according to the service requirement of the target object, for example, in practical application, a user needs to start a printer connected with a host end, and at the moment, the call plug-in of the printer is needed, namely, the call plug-in request of the printer is generated.
In addition, the plugin corresponding to the plugin calling request can also be an application plugin, for example, in practical application, when an administrator operates a host end (or a common user), the application a needs to be called, that is, a plugin calling request of the application a is generated, and the content of the plugin calling request can be determined according to practical situations.
Step S102, determining a light service plug-in to be called according to the call plug-in request;
the plug-in identification is contained in the plug-in calling request in the actual application, namely the light service plug-in which the target object needs to be called can be determined by identifying the plug-in identification.
In this step, the light service plug-in may be a PE (installation plug-in), a dll (dynamic library) file, or exe (executable).
Step S103, if the light service plug-in is found in the local plug-in library, acquiring operation environment information, and judging whether the light service plug-in is available according to the operation environment information;
In the embodiment of the application, whether the light service plugin required to be called by the target object is in a local plugin library is firstly judged, wherein the local plugin library can be a storage area in a host side and is used for storing the light service plugin, then if the light service plugin is found in the local plugin library, the running environment information of the current running environment is obtained, wherein the running environment information can comprise an application system (for example Windows) of the host side and a running object (for example C++ object) required by the plugin, finally whether the light service plugin is available is judged according to the running environment information, namely whether the running environment information is consistent with the configuration information of the light service plugin or not is judged, so that the light service plugin can be used in the running environment of the current running environment.
Step S104, if it is determined that the light service plug-in is available, packaging the light service plug-in into a light service for the target object.
In this step, when it is determined that the light service plugin is available, the light service plugin is packaged into a light service, and in practical application, after the light service plugin is packaged into the light service, the light service may be used as a target object in a host end for service support, or may be arranged to be online, and serve as a remote target object.
The light service plug-in can be packaged into light service when the user needs to call, or the light service can be packaged in advance for the user to select and use, and the specific situation can be determined according to the actual situation.
The embodiment of the application determines the light service plugin required by the target object by receiving the call plugin request input by the target object, determines the light service plugin to be called according to the call plugin request, firstly determines the light service plugin required by the target object, acquires the running environment information of the current running environment if the light service plugin is found in the local plugin library, judges whether the light service plugin is available according to the running environment information, ensures that the plugin required to be called can be started under the running environment of the current running environment, can also avoid the problem that the light service plugin collides with the three-party software running environment by locally acquiring the light service plugin, realizes the compatible running of the light service plugin in a mode of cross-browser and removing an ActiveX control (ocx control), and can realize the effect of high-cohesive low coupling by calling the light service plugin a mode of encapsulating the light service plugin into the light service if the light service plugin is determined to be available so as to be used by the target object, and even facing one-to-many scenes (such as multiple external devices in a station or installation devices in a station).
Further, the light service plug-ins in the local plug-in library may be downloaded by an administrator or provided from a manufacturer of the device, so that a security problem will be involved, for which, in yet another embodiment provided by the present application, the running environment information includes a plug-in dependency relationship and validity period and/or plug-in information of the light service plug-ins, and in step S103, the step of determining whether the light service plug-ins are available according to the running environment information includes:
Firstly, determining a target plugin on which the light service plugin depends according to the dependency relationship, and judging whether the target plugin is stored in the local plugin library;
In the embodiment of the application, whether the target plugin relied on by the light service plugin stores the target plugin needs to be judged, in practical application, the dependency relationship between the light service plugins can be the calling relationship of C++ objects, as shown in fig. 2, assuming that a plugin A and a plugin B exist in a host end, the C++ objects generated in the starting process of the plugin A are the service A and the service B, and the service C can be generated only by calling the service B in the running process of the plugin B, namely the plugin B depends on the plugin A, and the plugin A also needs to call the service C generated by the plugin B, so that the plugin A also depends on the plugin B.
Secondly, if the target plugin is stored in the local plugin library, judging whether the validity period of the light service plugin is positioned at the current moment or not;
In the embodiment of the application, the life cycle of the light service plug-in can be combined to judge whether the light service plug-in is located in the validity period, and particularly, the judgment result of whether the light service plug-in is valid can be determined by acquiring the comparison of the current moment and the validity period of the light service plug-in, so that the unavailable light service plug-in is prevented from being called.
In addition, whether the plug-in information is consistent with preset reference information is judged.
In the embodiment of the application, the plug-in information can comprise other plug-in related information such as a light service plug-in name, a version number, a calculated MD5 value, a dependent file, a light service plug-in accessible directory, a light service plug-in storage directory and the like, specifically, preset reference information is consistent with an authentication item contained in the plug-in information, open source information can be obtained from a manufacturer in advance, and can be recorded by a manager.
Further, in the embodiment of the present application, the authentication process for the light service plug-in the host side local plug-in library may further include an authentication process for the target plug-in that the light service plug-in depends on, as shown in fig. 3, including:
Step S301, determining a plurality of operation objects on which the light service plug-in depends according to the operation environment information;
In this step, the running environment information includes the running object information on which the light service plug-in depends, that is, a plurality of running objects (c++ objects) on which the light service plug-in depends can be directly determined through the running environment information.
In practical application, the running object may be an object obtained by encapsulating a target file on which a light service plug-in depends, for example, in a case of background registration, a plurality of plug-ins on which the light service plug-in depends may be multiple dll files, where dll is called a running object, and in the embodiment of the present application, the running object may not necessarily run independently, and a file on which the light service plug-in depends is a running object.
Step S302, determining a target plug-in for generating the operation objects aiming at each operation object which is not found in the operation objects;
In this step, multiple running objects on which the service plugin depends may be generated by the same target plugin or may be generated by different target plugins, and for this case, for each running object that is not found in the multiple running objects, a target plugin for generating the running object needs to be determined.
Step S303, judging whether the equipment identifier corresponding to the target plug-in is positioned in a permission list;
In this step, by judging whether the device identifier corresponding to the target plug-in is located in the permission list, unregistered devices can be screened out, so that the possibility of intrusion of the host side is reduced.
Step S304, if the device identifier corresponding to the target plug-in is located in the permission list, the target plug-in is operated to obtain the operation object generated by the target plug-in.
In practical application, the dependency relationship between the light service plugins may be a calling relationship of a c++ object, in the embodiment, as in the foregoing, it is assumed that a plugin a host side has a plugin a and a plugin B, where the c++ object generated in the enabling process of the plugin a is a service a and a service B, and in the running process of the plugin B, the plugin B needs to call the service B to generate a service C, that is, the plugin a depends on the plugin a, so that the plugin a also depends on the plugin B.
In addition, if the device identifier corresponding to the target plug-in is not located in the permission list, which indicates that the device to which the target plug-in belongs may have unsafe factors, in order to protect the host from being attacked by the malicious device, the target plug-in is not allowed to be invoked.
Along with the development of the internet of things technology, the types of external devices are promoted to be new, convenience is brought to people, and in practical application of business input, a desk client is generally connected with various external devices, such as an identity card reading device, a handwriting screen device, a high-speed camera device, a scanning device, a fingerprint recording device and the like. Therefore, in the embodiment of the present application, when the external device is detected, a process of performing authentication management on the device is further provided, and before receiving the call plug-in request entered by the target object, step S101, as shown in fig. 4, further includes:
step S410, obtaining device identifiers of a plurality of devices connected with the host end;
in this step, for the actual situation that one host end may be connected to multiple devices, the embodiment of the present application first determines the device identifiers of the multiple devices connected to the host end, and then performs authentication detection on the devices, so as to improve the security of the host end.
Step S420, determining equipment to be controlled according to the operation of selecting equipment identification by the target object;
in the embodiment of the application, an interface for selecting the equipment by the user can be provided, the equipment identification is corresponding to the operation of selecting the equipment by the user, and finally the equipment which the user needs to control is determined.
Step S421, if the equipment identifier of the equipment to be controlled is located in the permission list, generating a plug-in calling request according to the equipment identifier of the equipment to be controlled;
In the embodiment of the application, the permission list can be a permission list automatically generated after the background registers the light service plug-in and the equipment information, only the equipment which inputs the permission list is considered to be safe and usable, and a plug-in calling request corresponding to the equipment identification of the equipment to be controlled is generated.
In addition, step S422, if the device identifier of the device to be controlled is not located in the permission list, acquiring configuration information of the device to be controlled;
In this step, the configuration information of the device to be controlled may include information such as an input device type, a device model, manufacturer information, a vendor identification code VID (Vender ID), a product identification code PID (Product ID), etc., but is not limited thereto, and the specific content may be determined according to the actual situation.
Step S423, if the configuration information meets the preset registration condition, writing the device identifier of the device to be controlled into the permission list.
In the embodiment of the present application, the preset registration conditions may include a plurality of sub-conditions corresponding to the information items in the configuration information one by one, for example, in an actual case, the preset registration conditions include input device type adaptation, device model adaptation, manufacturer information adaptation, vendor identification code VID adaptation, and product identification code PID adaptation, and specific content included in the preset registration conditions may be determined according to the actual case.
In practical application, as shown in fig. 5, when a new external device D needs to be accessed to a host of a desk for use, first, the external device information needs to be registered in a management background, and information such as a device type, a device model, manufacturer information, a vendor identification code VID (Vender ID), a product identification code PID (Product ID) and the like is input and stored in a background database. Then, when the host agent invokes the external device D, the main flow is as shown in fig. 2, and the maintenance service module in the localized desktop light service obtains the external device information M2 of the host agent of the local agent, and encrypts the information M2 to obtain the encrypted information M2'. And secondly, the user transmits the encrypted information to the background service through a maintenance service in a running support middleware service in the background service system. Again, the background maintenance module decrypts the M2' information to obtain the plaintext information M2 after decryption. And finally, traversing and checking the registered device information in the database, and if the device D information exists in the database, enabling the device D to be a normal used safety device. Otherwise, the device is recorded as an unregistered device and is not used.
In an embodiment of the present application, a specific embodiment of a process for creating a local plugin library is further provided, as shown in fig. 6, including:
step S601, obtaining a plurality of light service plugins and plugin information of each light service plugin;
the plug-in information in this step may include a light service plug-in dependent operation object and access address and configuration information, but is not limited thereto, and the specific setting may be according to actual circumstances.
Step S602, determining the operation object, the access address and the configuration information which are depended on by the light service plug-in according to the plug-in information;
In this step, according to the content in the plug-in information, the running object and access address and configuration information on which the light service plug-in depends can be determined, so as to perform full-scale security authentication on the plug-in information.
Step S603, carrying out security verification on the configuration information;
step S604, if the configuration information passes the security verification, the running object is found in the local plugin library;
in this step, the step of performing security verification on the configuration information may specifically adopt a manner of traversing a preset white list, so as to determine whether the light service plugin is a registered security plugin, so as to prevent a malicious attack of the plugin from occurring.
The configuration information can comprise information such as a version number, a calculated MD5 value, a dependent file, a light service plug-in accessible catalog, a light service plug-in storage catalog and the like, and corresponding contents corresponding to various pieces of information in the configuration information are stored in a white list for comparison and verification of the configuration information contents.
Step S605, if the running object is not found in the local plugin library, acquiring the running object from a preset information library and storing the running object in the local plugin library;
In the embodiment of the application, if the operation object does not exist, the operation object can be obtained from a preset information base, wherein the preset information base can be arranged at a host end or can be an information base used for storing a target object in a cloud end, the operation object refers to a dependent file (such as a C++ object) on which a micro-service plug-in depends, after the operation object is obtained, the operation object is stored in a local client storage space, the storage part data cannot be modified and deleted for a common user, and an administrator user can directly conduct data arrangement and processing.
Step S606, storing the light service plugin in the local plugin library, and generating a call interface of the light service plugin according to the access address.
In practical application, the acquisition process of the light service plug-in can be realized through address analysis, and in order to ensure data security, the light service plug-in can also be realized through protocol analysis, and the specific realization process can be selected according to practical situations.
In the embodiment of the application, in order to protect the safety of the light service plugin and the local storage data, the access control is performed on the data, a storage space (namely a local plugin library) is newly built in the local client, and the local plugin library is used for storing the light service plugin and plugin information (such as data related to the localization middleware and.)
In practical application, as shown in fig. 7, in the background registration process, plug-in information of a light service plug-in to be registered is input, if an operation object determined according to the plug-in information is not in a local plug-in library, the operation object is acquired from a preset information library and stored in the local plug-in library (i.e. a database), in addition, the plug-in information can also be stored in the local plug-in library so as to be convenient for looking up the operation object on which the light service plug-in depends, or the plug-in information is stored in other storage areas of a host side, specifically, when the local client of the light service plug-in is updated according to the actual situation, a white list can be traversed first, if the dependency information of the micro service plug-in to be invoked is not present, if the dependency file of the micro service plug-in to be updated is present, after the operation object is acquired from the information library, the operation object is stored in the local client storage space, the storage part of data can be stored in the common user so as not to modify and delete the operation, the manager can directly carry out data arrangement and processing on the basis, or the plug-in the host side can be directly stored in other storage areas, if the directory is not accessed, the malicious information can be accessed in the actual situation, if the directory is not accessed, the directory information is directly needs to be accessed, and the malicious access information can be directly is accessed in the directory access process is directly, if the directory information is accessed.
Further, as shown in fig. 8, the embodiment of the present application further provides a method for determining that the configuration information passes the security check, including:
step S801, equipment identification, authorization information and dependent plug-in information are determined according to the configuration information;
Step S802, judging whether the equipment identifier is positioned in a permission list;
step S803, if the device identifier is in the permission list, determining whether the authorization information meets a preset authorization condition;
Step S804, if the authorization information meets a preset authorization condition, determining a dependent plug-in according to the dependent plug-in information, and if the dependent plug-in is located in the local plug-in library, determining that the configuration information passes the security check.
In the embodiment of the application, the configuration information comprises a device identifier, authorization information and dependent plug-in information, firstly, whether the device identifier is located in a permission list is judged, if the device identifier is located in the permission list, the device is proved to be the device which has completed registration at a host end, then, whether the authorization information accords with a preset authorization condition is judged, if the authorization information accords with the preset authorization condition, the light service plug-in is proved to pass through trust authorization of a manufacturer or the host end, finally, the dependent plug-in is determined according to the dependent plug-in information, if the dependent plug-in is located in a local plug-in library, the light service plug-in is proved to be capable of running at the host end, and finally, the configuration information is confirmed to pass through security verification.
Step S805, storing the light service plugin in the local plugin library.
In practical application, a new light service plug-in needs to be registered in a management background, and information such as a light service plug-in name, a version number, a digital signature, an MD5 value calculation, a dependent file, an accessible directory of the light service plug-in, a storage directory of the light service plug-in and the like is input and stored in a background database. Or generating a white list to prepare for the authentication part of the later light service plugin. The process includes an authentication management portion for the lightweight service plug-in, as shown in fig. 9, and described in detail below, the maintenance service accesses the local-end specific storage area in real time to discover the plug-in to be invoked locally. The local-end specific storage area refers to a storage area for access and storage control of a localization light service (localization middleware). The maintenance service obtains the plug-in related information, such as the light service plug-in name, version number, file MD5 value, light service plug-in digital signature, etc. And uploading the plug-in information to the background. Or download the whitelist from the background. Traversing the stored plug-in list (or traversing the whitelist downloaded locally) to see if there is a registered plug-in information list, allowing the light service plug-in to be invoked by the local side if the light service plug-in has been registered. Otherwise, the service plug-in is prompted to be an unregistered plug-in and is not called.
In still another embodiment of the present application, there is further provided an update management method of a light service plug-in, as shown in fig. 10, including:
Step S1001, traversing a plurality of the light services in the host side;
step S1002, when it is determined that the light service fails, of re-executing the step of encapsulating the light service plug-in as a light service to restart the light service;
In this step, the specific embodiment of determining the light service fault may be determined according to the actual situation, in the actual application, as shown in fig. 11, when a light service plug-in the host side fails (may fail in the device use process or may fail in the plug-in update process), the front end sends a request for seeking help from the host side, the request message is in json data format, encryption algorithm a is adopted to encrypt the management service receiving request message, decrypt the encrypted message to obtain a decrypted message, analyze the request message, the management service sends a request to the maintenance service, encrypts the message by encryption algorithm B, notifies the maintenance service to respond to the request sent by the front end of the service system, receives the request message, decrypts the encrypted message to obtain a decrypted message, parses the request message, and the maintenance service responds to the request, wherein the maintenance service captures local system information (such as system error information, CPU utilization rate, memory utilization rate and the like) and screen resource information, uploads the screen resource information to the rear station, and the maintenance service captures the real-time information, and the host side remote access to the screen resource is realized when the problem is pointed out that the host side accesses the screen resource. The log service can push the service, the plug-in call and the running log to the background, the background can analyze the log and check the real-time information of the local client screen errors at any time, the quick searching of the problems is realized, and the problems are efficiently positioned and solved.
Step S1003, when it is determined that the light service is online, performing update detection on the light service;
In practical application, in the background registration process, the dependency plug-in information of the light service plug-in to be registered is input, the dependency information is stored in a database, when the local client of the light service plug-in is updated, the white list is traversed firstly to obtain the dependency plug-in information of the micro service plug-in to be called, whether the dependency file of the light service plug-in to be updated exists locally or not, if the dependency file does not exist for updating, the dependency file is downloaded and stored in the local plug-in library of the local client, the data of the storage part cannot be modified and deleted for common users, and an administrator user can directly conduct data arrangement and processing. In the background registration process, the catalogue which is required to be accessed by the plug-in is input, and in the control loading process, the safety control of the catalogue is carried out, so that the access safety is ensured on one hand, and the attack behavior of a malicious plug-in is prevented on the other hand.
Step S1004, if it is determined to update the light service plug-in, acquiring an installation piece corresponding to the light service plug-in from an update database, and updating the light service by using the installation piece.
In practical application, according to the updating part of the authentication operation on the light service plugin, the updating service detects whether the local light service plugin is the latest light service plugin to be called in real time, as shown in fig. 12, specifically described below, the updating service acquires relevant information of the local light service plugin and the service, such as version number, MD5 value, digital signature and the like in real time, the updating service accesses a white list generated by a background in the downloading registration process to the local in real time, and the updating service traverses the white list to check whether the local light service plugin (or service) is the latest version and whether the updating flag bit needs to be updated. If an update is required, the update service sends a request to download the plug-in (e.g., C++ plug-in) or service for download. Meanwhile, the dependent file of the light service plug-in (or service) in the white list is checked, whether the dependent file exists locally or not is traversed, and if the dependent file does not exist locally, the update service continues to send a request for downloading the dependent file, and the dependent file is downloaded and updated.
In still another embodiment of the present application, there is further provided a localized plug-in service device, as shown in fig. 13, including:
The receiving module 01 is used for receiving a call plug-in request input by a target object;
a determining module 02, configured to determine a light service plugin to be invoked according to the invoke plugin request;
The judging module 03 is configured to obtain operating environment information if the light service plug-in is found in the local plug-in library, and judge whether the light service plug-in is available according to the operating environment information;
and the packaging module 04 is used for calling the light service plug-in to package the light service plug-in into a light service for the target object to use if the light service plug-in is determined to be available.
In yet another embodiment of the present application, there is provided an electronic device including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;
a memory for storing a computer program;
and the processor is used for realizing the localization plug-in service method according to the embodiment of the method when executing the program stored in the memory.
The electronic device provided by the embodiment of the application realizes the task of calling plug-in requests recorded by a target object by executing programs stored in a memory, determines a light service plug-in to be called according to the call plug-in requests, acquires operation environment information if the light service plug-in is found in a local plug-in library, judges whether the light service plug-in is available according to the operation environment information, calls the light service plug-in to package the light service plug-in into light service if the light service plug-in is determined to be available, so that the target object can use the request according to the task, reduces the collision probability of the plug-in and the three-party software operation environment by acquiring the plug-in locally, and can further ensure the availability of the called plug-in by combining the operation environment information. The communication bus 1140 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in fig. 14, but not only one bus or one type of bus.
The communication interface 1120 is used for communication between the electronic device and other devices described above.
The memory 1130 may include Random Access Memory (RAM) or non-volatile memory (non-volatilememory), such as at least one disk memory. Optionally, the memory may also be at least one memory device located remotely from the aforementioned processor.
The processor 1110 may be a general-purpose processor including a Central Processing Unit (CPU), a network processor (NetworkProcessor NP), a digital signal processor (DigitalSignalProcessing DSP), an application specific integrated circuit (ApplicationSpecificIntegratedCircuit ASIC), a Field-programmable gate array (Field-ProgrammableGateArray FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware components.
In yet another embodiment of the present application, there is also provided a computer readable storage medium having stored thereon a program of an information transmission method, which when executed by a processor, implements the steps of the localized plug-in service of the method embodiment.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.) means from one website, computer, server, or data center. Computer readable storage media can be any available media that can be accessed by a computer or data storage devices, such as servers, data centers, etc., that contain an integration of one or more available media. Usable media may be magnetic media (e.g., floppy disk, hard disk, magnetic tape), optical media (e.g., DVD), or semiconductor media (e.g., solid state disk SolidStateDisk (SSD)), among others.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein in the description of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application.
It should be noted that the above embodiments are merely for illustrating the technical solution of the present application and not for limiting the same, and although the present application has been described in detail with reference to the above embodiments, it should be understood by those skilled in the art that the technical solution described in the above embodiments may be modified or some or all of the technical features may be equivalently replaced, and these modifications or substitutions do not make the essence of the corresponding technical solution deviate from the scope of the technical solution of the embodiments of the present application.