CN113791795A

CN113791795A - Plug-in installation method, device, system, equipment and storage medium

Info

Publication number: CN113791795A
Application number: CN202010459484.1A
Authority: CN
Inventors: 田新超; 赵志远; 黄亚洲; 霍海涛
Original assignee: Beijing Qihoo Technology Co Ltd
Current assignee: Beijing Qihoo Technology Co Ltd
Priority date: 2020-05-26
Filing date: 2020-05-26
Publication date: 2021-12-14

Abstract

The invention discloses a method, a device, a system, equipment and a storage medium for installing a plug-in, wherein the method for installing the plug-in comprises the following steps: when an access request for accessing a client website is detected, acquiring prestored plugin configuration data and acquiring a first URL (uniform resource locator) corresponding to the access request; acquiring a plug-in file corresponding to the plug-in configuration data, and determining a second URL (uniform resource locator) corresponding to the plug-in file in the plug-in configuration data; if the first URL is successfully matched with the second URL, determining whether a plug-in file corresponding to the plug-in configuration data is installed or not according to the plug-in configuration data; and if the plug-in file is determined to be installed, installing the plug-in file according to the plug-in configuration data. The invention realizes the automatic installation of the plug-in file, avoids the condition that the service system is in a fault state because the service system can not automatically install the plug-in, thereby improving the operation efficiency of the service system in the client.

Description

Plug-in installation method, device, system, equipment and storage medium

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a method, an apparatus, a system, a device, and a storage medium for installing a plug-in.

Background

For enterprise user scenarios, because of different business system development technologies, plug-ins are often mounted in websites to complete business closed loops, and usually, when an individual browser user accesses the website, the user prompts the user to download or update the plug-ins. However, the formats of the plug-ins supported by different browsers are different, such as that the Trident kernel of an IE (Internet Explorer, IE Web browser) browser supports plug-ins in an ActiveX format, the Blink kernel of a Chrome browser supports plug-ins in a PPAPPI (Peer plug-in API)/NPAPI (Netscape plug-in API) format, and the Gecko kernel of a Firefox browser supports plug-ins in an NPAPI format. Different technical supports are provided by different plug-ins under different kernels, and corresponding operation systems are assisted to complete corresponding operations.

Generally, a World Wide Web (World Wide Web) service of a business system adds an object or an embedded tag declaration to a business code, and a part of the tag declaration is rendered by a plug-in to be displayed and interacted with correctly. An ActiveX plug-in of an IE kernel needs to be written into a system registry, and after a CLSID (class identifier) binding website is generated, the plug-in is automatically loaded when the website is accessed; the NPAPI and PPAPPI type plug-ins do not need to be written into a system registry, the downloaded plug-ins are directly stored in a browser plug-in directory, and the plug-ins are automatically loaded when the website is accessed after being bound with the website. For enterprise user scenes, because of different service system development technologies, plug-ins are often used to complete service closed loops, websites using an IE kernel usually prompt users to download and update plug-ins through browser pop-up windows, websites using a Chrome kernel do not prompt users to install plug-ins in a silent manner, and even a user computer terminal is required to have a corresponding local application program to render pages after the plug-ins are loaded on the browser.

Therefore, in an enterprise user scenario, when a developer behind a business system in operation does not have the capability to update a plug-in, that is, the business system cannot automatically install the plug-in, a vulnerability or other failure problem occurs in a business system website, and an enterprise user needs to pay more time and cost to change a business, that is, the business system cannot automatically install the plug-in, so that the business system is in a failure state.

Disclosure of Invention

The invention mainly aims to provide a plug-in installation method, a plug-in installation device, a plug-in installation system, plug-in installation equipment and a storage medium, and aims to solve the technical problem that a service system is in a fault state because the service system cannot automatically install the plug-ins in the prior art.

In order to achieve the above object, the present invention provides a method for installing a card, including the steps of:

when an access request for accessing a client website is detected, acquiring prestored plugin configuration data and acquiring a first URL (uniform resource locator) corresponding to the access request;

acquiring a plug-in file corresponding to the plug-in configuration data, and determining a second URL (uniform resource locator) corresponding to the plug-in file in the plug-in configuration data;

if the first URL is successfully matched with the second URL, determining whether a plug-in file corresponding to the plug-in configuration data is installed or not according to the plug-in configuration data;

and if the plug-in file is determined to be installed, installing the plug-in file according to the plug-in configuration data.

Optionally, if the first URL is successfully matched with the second URL, the step of determining whether to install the plug-in file corresponding to the plug-in configuration data according to the plug-in configuration data includes:

if the first URL is successfully matched with the second URL, acquiring a first operating system, a first kernel and installation data of the installed plug-in the client;

comparing the first operating system, the first kernel and the installation data with the plug-in configuration data respectively to obtain comparison results;

and determining whether to install the plug-in file corresponding to the plug-in configuration data according to the comparison result.

Optionally, the step of comparing the first operating system, the first kernel, and the installation data with the plug-in configuration data respectively to obtain a comparison result includes:

comparing the first operating system with a second operating system in the plug-in configuration data and comparing the first kernel with a second kernel in the plug-in configuration data;

and if the first operating system is consistent with a second operating system in the plug-in configuration data, the first kernel is consistent with a second kernel in the plug-in configuration data, and the installation data meets the installation conditions corresponding to the installation mechanism in the plug-in configuration data, obtaining a comparison result with successful comparison.

Optionally, if the first operating system is consistent with the second operating system in the plug-in configuration data, the first kernel is consistent with the second kernel in the plug-in configuration data, and the installation data meets the installation condition corresponding to the installation mechanism in the plug-in configuration data, the step of obtaining a comparison result with a successful comparison includes:

if the first operating system is consistent with a second operating system in the plug-in configuration data, and the first kernel is consistent with a second kernel in the plug-in configuration data, determining the plug-in type of the installed plug-in file in the client;

determining an installation condition corresponding to an installation mechanism in the plug-in configuration data according to the plug-in type;

and if the installation data meet the installation conditions, obtaining a comparison result of successful comparison.

Optionally, if it is determined to install the plug-in file, the step of installing the plug-in file according to the plug-in configuration data includes:

and if the installation of the plug-in file is determined, determining an installation mode for installing the plug-in file according to the plug-in configuration data, and installing the plug-in file according to the installation mode.

Optionally, the step of installing the plug-in file according to the installation manner includes:

if the installation mode is passive installation, outputting prompt information to prompt a user of the client to trigger an installation instruction according to the prompt information;

and if the installation instruction is detected, installing the plug-in file according to the installation instruction.

Optionally, before the step of obtaining the pre-stored plug-in configuration data after detecting the access request for accessing the client website, the method further includes:

when an acquisition request for acquiring the plug-in configuration data is detected, acquiring the plug-in configuration data in a server through the acquisition request;

and storing the plug-in configuration data into a preset array, wherein the plug-in configuration data corresponding to each plug-in file in the array is a JSON object.

Optionally, after detecting an obtaining request for obtaining the plug-in configuration data, the step of obtaining the plug-in configuration data in the server through the obtaining request includes:

when an obtaining request for obtaining the plug-in configuration data is detected, the plug-in configuration data is obtained in a redis cache in a server through the obtaining request, wherein in the redis cache, the plug-in configuration data is stored in a JSON array format.

when an acquisition request for acquiring the configuration data of the plug-in is detected, acquiring a protocol packet name corresponding to the acquisition request;

and determining a domain name corresponding to the server according to the protocol packet name, and acquiring the plug-in configuration data in the server through the domain name and the acquisition request.

Optionally, after an obtaining request for obtaining the plug-in configuration data is detected, before the step of obtaining the plug-in configuration data in the server through the obtaining request, the method further includes

Detecting whether the current time is the acquisition time corresponding to the plug-in configuration data;

and if the current time is detected to be the acquisition time corresponding to the plug-in configuration data, triggering an acquisition request for acquiring the plug-in configuration data.

In addition, in order to achieve the above object, the present invention further provides a method for installing a card, including:

after receiving an acquisition request for acquiring plugin configuration data sent by a client, a server sends the plugin configuration data and a plugin file corresponding to the plugin configuration data to the client according to the acquisition request;

when the client receives the plug-in configuration data and the plug-in file and detects an access request for accessing a client website, acquiring a second URL corresponding to the plug-in file in the plug-in configuration data, and detecting whether a first URL corresponding to the access request is successfully matched with the second URL;

and if the first URL is successfully matched with the second URL and the plug-in file is determined to be installed according to the plug-in configuration data, installing the plug-in file according to the plug-in configuration data.

Optionally, before the step of sending, by the server, the plug-in configuration data and the plug-in file corresponding to the plug-in configuration data to the client according to the acquisition request after receiving the acquisition request for acquiring the plug-in configuration data sent by the client, the method further includes:

and if the server side obtains plug-in configuration data according to the detected plug-in strategy configuration instruction, storing the plug-in configuration data into a preset database, and storing the plug-in configuration data into a redis cache in a JSON array format.

Optionally, the method for installing the plug-in further includes:

if a change instruction for changing the plug-in configuration data is detected, changing the plug-in configuration data according to the change instruction, wherein the change instruction at least comprises one of the following instructions: add instructions, modify instructions, delete instructions, and deactivate instructions.

In addition, to achieve the above object, the present invention provides an apparatus for mounting an insert, including:

the acquisition module is used for acquiring prestored plugin configuration data after detecting an access request for accessing a client website, acquiring a first URL corresponding to the access request and acquiring a plugin file corresponding to the plugin configuration data;

the determining module is used for determining a second URL corresponding to the plug-in file in the plug-in configuration data; if the first URL is successfully matched with the second URL, determining whether a plug-in file corresponding to the plug-in configuration data is installed or not according to the plug-in configuration data;

and the installation module is used for installing the plug-in file according to the plug-in configuration data if the plug-in file is determined to be installed.

In addition, in order to achieve the above object, the present invention further provides a system for installing a plug-in, where the system for installing a plug-in includes a client and a server;

the server is used for sending the plug-in configuration data and the plug-in file corresponding to the plug-in configuration data to the client according to an acquisition request after receiving the acquisition request for acquiring the plug-in configuration data sent by the client;

the client is used for acquiring a second URL (uniform resource locator) corresponding to the plug-in file in the plug-in configuration data after receiving the plug-in configuration data and the plug-in file and detecting an access request for accessing a client website, and detecting whether a first URL corresponding to the access request is successfully matched with the second URL; and if the first URL is successfully matched with the second URL and the plug-in file is determined to be installed according to the plug-in configuration data, installing the plug-in file according to the plug-in configuration data.

In addition, in order to achieve the above object, the present invention further provides a plug-in installation device, where the plug-in installation device includes a memory, a processor, and a plug-in installer that is stored in the memory and is executable on the processor, and the plug-in installer implements, when executed by the processor, a plug-in installation method corresponding to the federal learning server.

In addition, to achieve the above object, the present invention also provides a computer readable storage medium having stored thereon an installer of a plug-in, which, when executed by a processor, implements the steps of the installation method of the plug-in as described above.

According to the method and the device, after an access request for accessing a client website is detected, the pre-stored plug-in configuration data is obtained, the first URL corresponding to the access request is obtained, if the first URL is successfully matched with the second URL in the plug-in configuration data, and the plug-in file corresponding to the plug-in configuration data is determined to be installed according to the plug-in configuration data, the plug-in file is installed according to the plug-in configuration data, so that the automatic installation of the plug-in file is realized, the condition that a service system is in a fault state due to the fact that the service system cannot automatically install the plug-in is avoided, and the operation efficiency of the service system in the client is improved.

Drawings

FIG. 1 is a schematic flow chart diagram of a first embodiment of a plug-in installation method of the present invention;

FIG. 2 is a schematic flow chart diagram of a third embodiment of the plug-in installation method of the present invention;

FIG. 3 is a block diagram of a preferred embodiment of the card installation apparatus of the present invention;

fig. 4 is a schematic structural diagram of a hardware operating environment according to an embodiment of the present invention.

The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.

Detailed Description

It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

Referring to fig. 1, fig. 1 is a schematic flow chart illustrating a first embodiment of a method for installing a plug-in according to the present invention.

In accordance with the plug-in installation method provided by the present invention, it should be noted that although a logical order is shown in the flow chart, in some cases, the steps shown or described may be performed in an order different from that here.

The installation method of the plug-in is applied to a client, and the client can comprise a mobile terminal such as a mobile phone, a tablet computer, a notebook computer, a palm computer, a Personal Digital Assistant (PDA) and the like, and a fixed terminal such as a Digital TV, a desktop computer and the like. The installation method of the plug-in comprises the following steps:

step S11, when an access request for accessing the client website is detected, obtaining pre-stored plug-in configuration data, and obtaining a first URL corresponding to the access request.

When the client detects an access request for accessing the website, the client acquires pre-stored plug-in configuration data. It should be noted that, in this embodiment, the client is provided with a browser, and the website is a website of the business system corresponding to the browser. The access request can be triggered by a client user in the client, or the client receives an access request sent by other terminal equipment. The plug-in configuration data includes at least one of: the method comprises the steps of operating system corresponding to a plug-in, kernel, plug-in type, update range (install path type) corresponding to the plug-in file, plug-in installation package of the plug-in file, installation mechanism (issue), plug-in file name (file name), URL (Uniform Resource Locator) of corresponding website (match URL), plug-in download path (down load URL), check value (md5) of the plug-in file, plug-in Resource type (mime _ type), ID (plugin) of application corresponding to the plug-in to take effect, plug-in name (plugin name), prompt state (prefab), plug-in sequence number (range _ type), plug-in version number (version) and installation time (install time) of the plug-in file. Further, if the plug-in file corresponding to the plug-in configuration data needs a registry, the plug-in configuration data may further include a registry identifier (cls id).

Wherein, the operating system can be a Windows system or a Linux system, etc.; the kernel can be Trident kernel, Gecko kernel, Blink kernel and the like; the plug-in type can be ActiveX-IE, NPAPI-Chromium and PPAPPI-Chromium, etc., and the plug-in type includes but is not limited to ActiveX plug-in, NPAPI plug-in and PPAPPI plug-in; the updating range can be global updating, application group updating and the like; the plug-in installation package is an expression form of plug-in files, and when the plug-in installation package is an ActiveX plug-in, the corresponding plug-in files can be files with extension names such as 'exe', 'cab', 'msi' and the like; under a windows system, the corresponding plug-in file of the NPAPI/PPAPPI plug-in can be a file with an extension name of "exe" or "msi"; under the Linux system, the NPAPI plugin or PPAPI plugin corresponds to a plugin file with an extension of "rpm" or "deb". The installation mechanisms corresponding to different types of plug-in files are different, and when the plug-in files are ActiveX plug-ins and the installation mechanisms of the plug-in files are plug-in version numbers and/or plug-in file changes, the plug-in files in the client side need to be updated; when the plug-in file is an NPAPI plug-in or a PPAPPI plug-in, and the installation mechanism is plug-in version number updating, the plug-in file in the client needs to be updated. In this embodiment, the check value of the plug-in file is represented by an md5 value, and in other embodiments, the check value of the plug-in file may also be represented by other hash values, and each plug-in file has a unique check value. The plug-in file is stored in the file server of the server, and the client can obtain the plug-in file corresponding to the plug-in configuration data from the file server of the server through the plug-in download path in the plug-in configuration data. The registry mark can uniquely identify one registry, and the marks corresponding to different registries are different. It should be noted that the plugin configuration data corresponding to each plugin file is preset, and the expression form of each plugin configuration data may be set according to specific needs, and other plugin configuration data is not described in this embodiment.

In this embodiment, the representation form of the operating system identifier is not limited, the operating system of the client may be uniquely determined by the operating system identifier, and the plug-in type corresponding to the client browser may be determined by the version of the client browser. When the client detects the access request, the client obtains a URL corresponding to the access request, and records the URL corresponding to the access request as a first URL, where it can be understood that the URL is a URL of a website that the access request needs to access.

Step S13, obtaining the plug-in file corresponding to the plug-in configuration data, and determining a second URL corresponding to the plug-in file in the plug-in configuration data.

Step S15, if the first URL is successfully matched with the second URL, determining whether to install a plug-in file corresponding to the plug-in configuration data according to the plug-in configuration data.

And after the client side obtains the plug-in configuration data, the client side obtains a plug-in file corresponding to the plug-in configuration data, obtains a URL corresponding to the plug-in file in the plug-in configuration data, marks the URL determined from the plug-in configuration data as a second URL, and detects whether the first URL is the same as the second URL. It should be noted that there exists a URL in each piece of plug-in configuration data, where the URL is the URL of the website where the plug-in configuration data corresponds to the plug-in file to be installed. If the client detects that the first URL is the same as the second URL, the client determines that the first URL is successfully matched with the second URL; and if the client detects that the first URL is not identical to the second URL, the client determines that the first URL and the second URL are failed to be matched. It is understood that when the first URL and the second URL are the same, it indicates that the plug-in configuration data corresponds to a plug-in that needs to be installed in the website. And if the client determines that the first URL and the second URL are successfully matched, the client determines whether the plug-in files corresponding to the plug-in configuration data are installed or not according to the plug-in configuration data, wherein each plug-in file has corresponding plug-in configuration data. It should be noted that, in order to facilitate management and installation of the plug-ins, in this embodiment, the plug-in files are packaged into the executable program installation package, that is, the plug-in files are packaged into the plug-in installation package. Further, if the client determines that the first URL is different from the second URL, the client determines that the plug-in file is not required to be installed at present, and may directly execute the access request in the website and open the webpage corresponding to the access request.

Further, step S15 includes:

step a, if the first URL is successfully matched with the second URL, acquiring a first operating system, a first kernel and installation data of the installed plug-in the client.

Further, if the client determines that the first URL is successfully matched with the second URL in the plug-in configuration data, the client obtains its operating system type and kernel type, and records its operating system type as the first operating system, and records its kernel type as the first kernel, and obtains installation data of the installed plug-in the website, where the installation data includes, but is not limited to, a plug-in version number and a plug-in file, in this embodiment, the plug-in file may be represented by a check value of the plug-in file, and at this time, the installation data includes, but is not limited to, the plug-in version number and the check value. It can be understood that if the check values corresponding to two plug-in files are different, it indicates that the contents of the two plug-in files are different; if the corresponding check values of the two plug-in files are the same, the content of the two plug-in files is the same.

And b, comparing the first operating system, the first kernel and the installation data with the plug-in configuration data respectively to obtain a comparison result.

And d, determining whether to install the plug-in file corresponding to the plug-in configuration data according to the comparison result.

After the client obtains the first operating system, the first kernel and the installation data, the client compares the first operating system, the first kernel and the installation data with the plug-in configuration data respectively to obtain a comparison result. In this embodiment, there are two types of comparison results, one is that the full comparison of the corresponding data in the first operating system, the first kernel, the installation data, and the plug-in configuration data is successful, and a comparison result with successful comparison is obtained, where the corresponding result identifier is a successful identifier, and the other is that the comparison of the corresponding data in the first operating system, the first kernel, the installation data, and the plug-in configuration data is failed, and a comparison result with failed comparison is obtained, and a corresponding result identifier is a failed identifier. In this embodiment, the expression of the success flag and the failure flag is not limited. And after the client side obtains the comparison result, the client side determines whether the plug-in file corresponding to the plug-in configuration data is installed or not according to the comparison result. Specifically, when the comparison result is that the comparison is successful, the client determines that a plug-in file corresponding to the plug-in configuration data is installed in a browser corresponding to the website; and when the comparison result is that the comparison fails, the client determines that the plug-in file corresponding to the plug-in configuration data is not installed in the browser corresponding to the website.

Further, step b comprises:

step b1, comparing the first operating system with the second operating system in the plug-in configuration data, and comparing the first kernel with the second kernel in the plug-in configuration data.

Step b3, if the first operating system is consistent with the second operating system in the plug-in configuration data, the first kernel is consistent with the second kernel in the plug-in configuration data, and the installation data meets the installation condition corresponding to the installation mechanism in the plug-in configuration data, obtaining a comparison result with successful comparison.

Specifically, the client acquires an operating system and a kernel in the plug-in configuration data, records the operating system acquired from the plug-in configuration data as a second operating system, compares the first operating system with the second operating system, and compares the first kernel with the second kernel. And if the first operating system and the second operating system are not the same operating system, the client determines that the first operating system and the second operating system are not the same. If the first kernel and the second kernel are the same kernel, if the first kernel and the second kernel are both Trident kernels, the client determines that the first kernel and the second kernel are consistent; and if the first kernel and the second kernel are not the same kernel, the client determines that the first kernel and the second kernel are inconsistent.

And when the client determines that the first operating system is consistent with the second operating system and the first kernel is consistent with the second kernel, the client judges whether the installation data meets the installation conditions corresponding to the installation mechanism in the case strategy configuration data. If the client determines that the installation data meet the installation conditions corresponding to the installation mechanism, the client obtains a comparison result of successful comparison; if the client determines that the installation data does not satisfy the installation conditions corresponding to the installation mechanism, the client obtains a comparison result of failed comparison. Further, if the client determines that the first operating system is inconsistent with the second operating system and/or the first kernel is inconsistent with the second kernel, at this time, the client obtains a comparison result of the comparison failure regardless of whether the installation data meets the installation condition corresponding to the installation mechanism. It can be understood that, if the plug-in file of the a operating system is installed in the browser corresponding to the B operating system, or the plug-in file of the a kernel is installed in the browser corresponding to the B kernel, the browser cannot normally open the web page.

Further, step b1 includes:

step b11, if the first operating system is consistent with the second operating system in the plug-in configuration data, and the first kernel is consistent with the second kernel in the plug-in configuration data, determining the plug-in type of the installed plug-in file in the client.

Step b13, determining the installation condition corresponding to the installation mechanism in the plug-in configuration data according to the plug-in type.

And b15, if the installation data meet the installation conditions, obtaining a comparison result with successful comparison.

Further, if the client determines that the first operating system is consistent with the second operating system in the plug-in configuration data and the first kernel is consistent with the second kernel in the plug-in configuration data, the client determines the plug-in type of the installed plug-in file, that is, determines the plug-in type of the installed plug-in file in the website corresponding to the access request, and determines the installation condition corresponding to the installation mechanism in the plug-in configuration data according to the plug-in type. In this embodiment, when the plug-in type is an ActiveX plug-in, the installation condition corresponding to the installation mechanism is a plug-in version update and/or a plug-in file update, and specifically, the client acquires a first version number of an installed plug-in file and a first check value of the plug-in file, and acquires a second version number and a second check value in the plug-in configuration data. If the installation condition is plug-in version updating and the client detects that the first version number is smaller than the second version number, the client determines that the installation data meets the installation condition, and if the client detects that the first version number is larger than or equal to the second version number, the client determines that the installation data does not meet the installation condition; if the installation condition is plug-in file updating and the client detects that the first check value and the second check value are not equal, the client determines that the installation data meet the installation condition, and if the client detects that the first check value and the second check value are equal, the client determines that the installation data do not meet the installation condition; if the installation condition is plug-in version updating and plug-in file updating, and the client detects that the first version number is smaller than the second version number and the first check value is not equal to the second check value, the client determines that the installation data meets the installation condition, and if the client detects that the first version number is larger than or equal to the second version number and/or the first check value is equal to the second check value, the client determines that the installation data does not meet the installation condition.

And when the plug-in type is the NPAPI plug-in or the PPAPPI plug-in, the installation condition corresponding to the installation mechanism is the update of the version of the plug-in. The specific process of updating the installation condition as the plug-in version is already described in detail when the plug-in type is an ActiveX plug-in, and is not repeated here. When the client determines that the installation data meet the installation conditions, the client obtains a comparison result of successful comparison; and when the client determines that the installation data does not meet the installation conditions, the client obtains a comparison result of failed comparison.

And step S17, if the plug-in file is determined to be installed, installing the plug-in file according to the plug-in configuration data.

And if the client determines that the plug-in file corresponding to the plug-in configuration data needs to be installed, the client installs the plug-in file according to the plug-in configuration data. Specifically, in the process of installing the plug-in file according to the plug-in configuration data, the client can obtain the update range in the plug-in configuration data, and install the plug-in file through the update range, for example, when the update range is global update, the client can directly install the whole plug-in file; when the update range is application update, the client needs to acquire an application of the plug-in file to be updated and install a file corresponding to the application to be updated, namely, the file corresponding to the application to be updated replaces a file corresponding to the application in the installed plug-in file; and when the updating range is the application group updating, the client acquires the application group needing updating in the plug-in file, and installs the file corresponding to the application group needing updating. Further, the client can also obtain the installation time in the plug-in configuration data, and judge whether the current time is the installation time of the plug-in file or not according to the installation time; if the client determines that the current time is the installation time of the plug-in file, the client installs the plug-in file; if the client determines that the current time is not the installation time of the plug-in file, the client continuously judges whether the current time is the installation time of the plug-in file. For example, the installation timing may be set to a fixed time point of day, or may be set when a specific command is detected.

And when the client successfully installs the plug-in file, namely the plug-in file corresponding to the plug-in configuration data is successfully installed in the browser corresponding to the website, the client opens the webpage corresponding to the access request through the website of the browser for installing the plug-in file so as to respond to the access request.

Further, step S17 includes:

and e, if the installation of the plug-in file is determined, determining an installation mode for installing the plug-in file according to the plug-in configuration data, and installing the plug-in file according to the installation mode.

Further, if the client determines that the plug-in file is to be installed, the client determines the installation mode of the plug-in file according to the installation mode in the plug-in configuration data, and installs the plug-in file corresponding to the plug-in configuration data according to the determined installation mode. The mounting manner includes, but is not limited to, active mounting and passive mounting. Specifically, when the client determines that the installation mode of the add-in file is active installation, the client directly installs the add-in file in the background, and the installation process of the add-in file is invisible to the user, that is, the user does not feel the installation process of the add-in file.

Further, the step of installing the plug-in file according to the installation manner comprises:

and f, if the installation mode is passive installation, outputting prompt information to prompt a user of the client to trigger an installation instruction according to the prompt information.

And g, if the installation instruction is detected, installing the plug-in file according to the installation instruction.

And if the client determines that the installation mode is passive installation, the client generates prompt information and outputs the prompt information so as to prompt a client user to trigger an installation instruction according to the prompt information. Specifically, after the client user views the prompt message, the client user may trigger an installation instruction through an entity key or a virtual key in the client. In this embodiment, the output mode of the client for outputting the prompt information is not limited. And when the client detects the installation instruction, the client installs the plug-in file according to the installation instruction.

According to the method and the device, after an access request for accessing a client website is detected, the pre-stored plug-in configuration data is obtained, the first URL corresponding to the access request is obtained, if the first URL is successfully matched with the second URL in the plug-in configuration data, and the plug-in file corresponding to the plug-in configuration data is determined to be installed according to the plug-in configuration data, the plug-in file is installed according to the plug-in configuration data, so that the automatic installation of the plug-in file is achieved, the situation that a service system is in a fault state due to the fact that the service system cannot automatically install the plug-in is avoided, and therefore the operation efficiency of the service system in the client is improved.

It can be understood that, because the embodiment implements automatic installation of the plug-in file, it is avoided that when a user accesses a website corresponding to the business system, the access fails or the access efficiency is low because the corresponding plug-in is not installed or the plug-in is not updated, the success rate and the response efficiency of the client for responding to the access request are improved, and the user does not need to go to other websites to search for the required plug-in, thereby reducing the time required for opening the corresponding webpage when the user accesses the website corresponding to the business system.

Further, a second embodiment of a method of mounting an insert is presented. The second embodiment of the mounting method of the card differs from the first embodiment of the mounting method of the card in that the mounting method of the card further comprises:

and h, when an acquisition request for acquiring the plug-in configuration data is detected, acquiring the plug-in configuration data in the server through the acquisition request.

When the client detects an acquisition request for acquiring the plug-in configuration data, the client acquires the plug-in configuration data in the server through the acquisition request. The obtaining request carries information such as an operating system identifier of the client and a browser version of the client, and the required plug-in strategy configuration information can be obtained in the server by obtaining the information carried by the request. The acquisition request can be triggered in the client according to the requirement of a client user, or can be triggered in a timing task preset in the client in a timing mode.

Further, the step h includes:

step h2, when an obtaining request for obtaining the plug-in configuration data is detected, obtaining the plug-in configuration data in a redis cache of the server through the obtaining request, wherein in the redis cache, the plug-in configuration data is stored in a JSON array format.

When the client detects an acquisition request for acquiring the plug-in configuration data, the client acquires the plug-in configuration data in a redis cache in the server through the acquisition request, wherein in the redis cache, the plug-in configuration data is stored in a JSON (Java Script Object Notation) array format. The plug-in configuration data is acquired in the redis cache of the server instead of after the plug-in configuration data required to be acquired is found in the mysql database of the server, so that the acquisition efficiency of the client for acquiring the plug-in configuration data is improved.

Further, the step h further comprises:

step h4, when detecting the obtaining request for obtaining the plug-in configuration data, obtaining the protocol packet name corresponding to the obtaining request.

Step h6, determining the domain name corresponding to the server according to the protocol packet name, and acquiring the plug-in configuration data in the server through the domain name and the acquisition request.

Further, when the client detects an acquisition request for acquiring policy configuration data, the client acquires a protocol packet name corresponding to the acquisition request, and it should be noted that a communication protocol between the client and the server can be determined by the protocol packet. After the client acquires the protocol packet name, the client acquires a domain name in the protocol packet name, determines the acquired domain name as a domain name corresponding to the server, and establishes a connection relationship with the server through the domain name. After the connection relation between the client and the server is established, the client sends an acquisition request to the server so as to acquire the plug-in configuration data in the server through the acquisition request. It is understood that the domain name is part of the protocol package name.

Step i, storing the plug-in configuration data into a preset array, wherein the plug-in configuration data corresponding to each plug-in file in the array is a JSON object.

In this embodiment, the array for storing the plug-in configuration data is a JSON array because the plug-in configuration data is a JSON object, in which the plug-in configuration data corresponding to each plug-in file is a JSON object and each JSON object has a corresponding URL. When the client needs to use the plug-in configuration data, the client acquires the plug-in configuration data from the array.

It should be noted that after the client obtains the plug-in configuration data from the server, the client obtains the plug-in file corresponding to the plug-in configuration data from the server according to the plug-in download path in the plug-in configuration data, and stores the array corresponding to the plug-in configuration data and the plug-in file in a specific memory directory in an associated manner, so that when the plug-in file needs to be installed, the plug-in configuration data and the corresponding plug-in file are obtained according to the memory target.

In this embodiment, the client stores the acquired plugin configuration data in the array as a JSON object, so that the required plugin configuration data can be quickly acquired in the array when the plugin configuration data needs to be acquired, thereby improving the acquisition efficiency of the plugin configuration data.

Further, the installation method of the plug-in unit further comprises the following steps:

and j, detecting whether the current time is the acquisition time corresponding to the plug-in configuration data.

And m, if the current time is detected to be the acquisition time corresponding to the plug-in configuration data, triggering an acquisition request for acquiring the plug-in configuration data.

Further, the client detects, in a timed manner or in real time, whether the current time is the acquisition time corresponding to the plug-in configuration data, in this embodiment, the client acquires the plug-in configuration data from the server in a timed manner, a duration corresponding to the timed manner may be set according to specific needs, and the duration corresponding to the timed manner is not specifically limited in this embodiment. Specifically, the client records the historical acquisition time of acquiring the plug-in configuration data from the server last time, calculates the time difference between the historical acquisition time and the current time, and if the time difference is equal to or greater than the time length corresponding to the timing, the client can determine that the current time is the acquisition time corresponding to the plug-in configuration data; if the time difference is smaller than the time length corresponding to the timing, the client determines that the current time is not the acquisition time corresponding to the plug-in configuration data. If the client detects that the current time is the acquisition time corresponding to the plug-in configuration data, the client automatically triggers an acquisition request for acquiring the plug-in configuration data; and if the client detects that the current time is not the acquisition time corresponding to the plug-in configuration data, the client continuously detects whether the current time is the acquisition time corresponding to the plug-in configuration data. It is understood that, in this embodiment, the client will periodically poll the interface of the server to obtain the latest plugin configuration data and plugin files. It should be noted that, each time the client acquires the plug-in configuration data from the server, the client may acquire the corresponding plug-in file again according to the plug-in download path in the newly acquired plug-in configuration data.

In this embodiment, the client acquires the plug-in configuration data from the server at regular time, so as to update the plug-in the client browser at regular time according to the plug-in configuration data acquired at regular time, thereby further improving response efficiency of responding to the access request.

Further, a third embodiment of a method of mounting an insert is presented. Referring to fig. 2, the method of installing the insert further includes:

step S31, after receiving the request for obtaining the plug-in configuration data sent by the client, the server sends the plug-in configuration data and the plug-in file corresponding to the plug-in configuration data to the client according to the request for obtaining.

Step S33, when the client receives the plug-in configuration data and the plug-in file and detects an access request for accessing a client website, acquiring a second URL corresponding to the plug-in file in the plug-in configuration data, and detecting whether a first URL corresponding to the access request matches the second URL successfully.

Step S35, if the first URL and the second URL are successfully matched and the plug-in file is determined to be installed according to the plug-in configuration data, the plug-in file is installed according to the plug-in configuration data.

And after receiving an acquisition request for acquiring the plug-in configuration data sent by the client, the server sends the plug-in configuration data and a plug-in file corresponding to the plug-in configuration data to the client according to the acquisition request. The plug-in configuration data is preset by a server user and is stored in the server. When the client receives the plug-in configuration data and the plug-in file and detects an access request for accessing the client website, the client acquires a second URL corresponding to the plug-in file in the plug-in configuration data and detects whether the first URL and the second URL of the access request are successfully matched. And if the client detects that the first URL is successfully matched with the second URL in the plug-in configuration data and determines that the corresponding plug-in file needs to be installed according to the plug-in configuration data, the client installs the plug-in file corresponding to the plug-in configuration data according to the plug-in configuration data. It should be noted that the specific implementation processes of step S33 and step S35 have been described in detail in the above embodiments, and are not repeated herein.

and n, if the server side obtains plug-in configuration data according to the detected plug-in strategy configuration instruction, storing the plug-in configuration data into a preset database, and storing the plug-in configuration data into a redis cache in a JSON array format.

Further, the server detects whether a plug-in policy configuration instruction for configuring the plug-in configuration data is detected, and the plug-in policy configuration instruction is triggered by a server user according to needs. When the server side detects a plug-in strategy configuration instruction for configuring the plug-in configuration data, the server side obtains the plug-in configuration data according to the plug-in strategy configuration instruction, stores the plug-in configuration data into a preset database which is preset, and stores a plug-in file corresponding to the plug-in configuration data into a corresponding file server, wherein the file server is a database which is used for storing the plug-in file in the server side, and the preset database for storing the plug-in configuration data can be a mysql database or other databases. After the server side obtains the plug-in configuration data, the server side stores the plug-in configuration data into a redis cache in a JSON array format, so that when the client side needs to obtain the plug-in configuration data, the server side obtains the plug-in configuration data from the redis cache and sends the plug-in configuration data to the client side, the plug-in configuration data does not need to be obtained from a preset database and sent to the client side, and the efficiency of obtaining the plug-in configuration data in the redis cache is higher than that of obtaining the plug-in configuration data in the preset database, so that the sending efficiency of sending the plug-in configuration data by the server side is improved, and the obtaining efficiency of obtaining the plug-in configuration data by the client side is improved.

step o, if a change instruction for changing the plug-in configuration data is detected, changing the plug-in configuration data according to the change instruction, wherein the change instruction at least comprises one of the following instructions: add instructions, modify instructions, delete instructions, and deactivate instructions.

Further, when the server detects a change instruction for changing the configuration data of the plug-in, the server changes the configuration data of the plug-in according to the update instruction, wherein the change instruction at least comprises one of the following instructions: add instructions, modify instructions, delete instructions, and deactivate instructions. The adding instruction may be to add new plug-in configuration data to the plug-in configuration data, and if there is no installation time in the plug-in configuration data, the server may add an installation time in the plug-in configuration data according to the adding instruction. The modification instruction is to modify the original plug-in configuration data of the server, for example, the server modifies the update range and/or the plug-in name of the plug-in configuration data according to the modification instruction. The deleting instruction is to delete data in the plugin configuration data, for example, the server deletes an update range and/or a plugin serial number in the plugin configuration data according to the deleting instruction, and when the plugin configuration data does not have the update range, it indicates that the plugin file corresponding to the plugin configuration data needs to be updated globally. The stop instruction is to stop using the plug-in configuration data, for example, when the server side makes the plug-in configuration data in a stop state according to the stop instruction, the server side does not send the plug-in configuration data in the stop state to the client side. Further, after the server side changes the plug-in configuration data, the server side stores the changed plug-in configuration data into a preset database and a redis cache. Further, after the server side obtains the changed plug-in configuration data, the server side can also directly send the changed plug-in configuration data to the client side.

According to the method and the device, the plug-in configuration data are updated through the change instruction, the plug-in configuration data are prevented from being unchanged, and therefore the plug-in configuration data can be updated regularly, the client can obtain the latest plug-in configuration data, and the update efficiency of the plug-in of the client is improved.

Further, there is provided an insert mounting apparatus, referring to fig. 3, including:

the acquisition module 10 is configured to, after detecting an access request for accessing a client website, acquire pre-stored plug-in configuration data, acquire a first URL corresponding to the access request, and acquire a plug-in file corresponding to the plug-in configuration data;

a determining module 30, configured to determine a second URL corresponding to the plug-in file in the plug-in configuration data; if the first URL is successfully matched with the second URL, determining whether a plug-in file corresponding to the plug-in configuration data is installed or not according to the plug-in configuration data;

and the installing module 50 is configured to install the plug-in file according to the plug-in configuration data if it is determined that the plug-in file is installed.

Further, the determining module 30 includes:

a first obtaining unit, configured to obtain, if the first URL is successfully matched with the second URL, a first operating system, a first kernel of the client, and installation data of an installed plug-in the client;

the comparison unit is used for comparing the first operating system, the first kernel and the installation data with the plug-in configuration data respectively to obtain a comparison result;

and the first determining unit is used for determining whether the plug-in file corresponding to the plug-in configuration data is installed or not according to the comparison result.

Further, the comparing unit is further configured to compare the first operating system with a second operating system in the plug-in configuration data, and compare the first kernel with a second kernel in the plug-in configuration data; and if the first operating system is consistent with a second operating system in the plug-in configuration data, the first kernel is consistent with a second kernel in the plug-in configuration data, and the installation data meets the installation conditions corresponding to the installation mechanism in the plug-in configuration data, obtaining a comparison result with successful comparison.

Further, the comparing unit is further configured to determine a plug-in type of the installed plug-in file in the client if the first operating system is consistent with a second operating system in the plug-in configuration data, and the first kernel is consistent with a second kernel in the plug-in configuration data; determining an installation condition corresponding to an installation mechanism in the plug-in configuration data according to the plug-in type; and if the installation data meet the installation conditions, obtaining a comparison result of successful comparison.

Further, the installation module 50 is further configured to determine an installation manner for installing the plug-in file according to the plug-in configuration data if it is determined that the plug-in file is installed, and install the plug-in file according to the installation manner.

Further, the installation module 50 includes:

the output unit is used for outputting prompt information if the installation mode is passive installation so as to prompt a user of the client to trigger an installation instruction according to the prompt information;

and the installation unit is used for installing the plug-in file according to the installation instruction if the installation instruction is detected.

Further, the obtaining module 10 is further configured to obtain the plug-in configuration data in the server through the obtaining request after detecting the obtaining request for obtaining the plug-in configuration data;

the mounting device of the plug-in unit further comprises:

and the storage module is used for storing the plug-in configuration data into a preset array, wherein the plug-in configuration data corresponding to each plug-in file in the array is a JSON object.

Further, the obtaining module 10 is further configured to, after an obtaining request for obtaining plug-in configuration data is detected, obtain the plug-in configuration data in a redis cache in the server through the obtaining request, where in the redis cache, the plug-in configuration data is stored in a JSON array format.

Further, the obtaining module 10 further includes:

the second acquisition unit is used for acquiring a protocol packet name corresponding to an acquisition request after the acquisition request for acquiring the plug-in configuration data is detected;

the second determining unit is used for determining the domain name corresponding to the server according to the protocol packet name;

the second obtaining unit is further configured to obtain the plug-in configuration data in the server through the domain name and the obtaining request.

Further, the mounting device of the insert further comprises:

the detection module is used for detecting whether the current time is the acquisition time corresponding to the plug-in configuration data;

and the triggering module is used for triggering an acquisition request for acquiring the plug-in configuration data if the current time is detected to be the acquisition time corresponding to the plug-in configuration data.

The specific implementation of the mounting apparatus for a card according to the present invention is substantially the same as the steps in the first and second embodiments of the mounting method for a card, and will not be described herein again.

In addition, an installation system of the plug-in is also provided, and the installation system of the plug-in comprises a client and a server;

Further, the server is further configured to store the plug-in configuration data into a preset database and store the plug-in configuration data into a redis cache in a JSON array format if the plug-in configuration data is obtained according to the detected plug-in policy configuration instruction.

Further, the server is further configured to, if a change instruction for changing the plug-in configuration data is detected, change the plug-in configuration data according to the change instruction, where the change instruction at least includes one of the following instructions: add instructions, modify instructions, delete instructions, and deactivate instructions.

The specific implementation of the plug-in installation system according to the present invention is substantially the same as the steps in the third embodiment of the plug-in installation method described above, and details are not repeated here.

In addition, a mounting device of the plug-in is also provided. As shown in fig. 4, fig. 4 is a schematic structural diagram of a hardware operating environment according to an embodiment of the present invention.

Fig. 4 is a schematic structural diagram of a hardware operating environment of the plug-in installation device. The installation device of the plug-in according to the embodiment of the invention can be a terminal device such as a PC, a portable computer and the like.

As shown in fig. 4, the mounting apparatus of the card may include: a processor 1001, such as a CPU, a memory 1005, a user interface 1003, a network interface 1004, a communication bus 1002. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a storage device separate from the processor 1001.

It will be appreciated by those skilled in the art that the mounting arrangement configuration of the insert shown in figure 4 does not constitute a limitation of the mounting arrangement of the insert and may include more or fewer components than shown, or some components may be combined, or a different arrangement of components.

As shown in fig. 4, a memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and an installer of a plug-in. The operating system is a program for managing and controlling hardware and software resources of the installation device of the plug-in, and supports the installation program of the plug-in and the running of other software or programs.

In the installation apparatus of the plug-in shown in fig. 4, the user interface 1003 is mainly used for connecting to the server and performing data communication with the server, for example, obtaining plug-in configuration data from the server; the network interface 1004 is mainly used for the background server and performs data communication with the background server; the processor 1001 may be configured to call an installer of the plug-in stored in the memory 1005 and perform the steps of the plug-in installation method as described above.

The specific implementation of the installation device of the plug-in unit according to the present invention is substantially the same as the embodiments of the installation method of the plug-in unit, and is not described herein again.

Furthermore, an embodiment according to the present invention also provides a computer-readable storage medium, on which an installer of a plug-in is stored, which, when executed by a processor, implements the steps of the installation method of the plug-in as described above.

The specific implementation of the computer-readable storage medium according to the present invention is substantially the same as the embodiments of the plug-in installation method described above, and is not described herein again.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.

The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims

1. A method of installing a card, comprising the steps of:

2. The method for installing the plugin according to claim 1, wherein if the first URL and the second URL are successfully matched, the step of determining whether to install the plugin file corresponding to the plugin configuration data according to the plugin configuration data includes:

3. The method for installing the plug-in according to claim 2, wherein the step of comparing the first operating system, the first kernel, and the installation data with the plug-in configuration data to obtain comparison results comprises:

4. The method for installing a plug-in according to claim 3, wherein if the first operating system is consistent with a second operating system in the plug-in configuration data, the first kernel is consistent with a second kernel in the plug-in configuration data, and the installation data satisfies an installation condition corresponding to an installation mechanism in the plug-in configuration data, the step of obtaining a comparison result with a successful comparison includes:

5. The method for installing a plug-in according to claim 1, wherein if it is determined that the plug-in file is installed, the step of installing the plug-in file according to the plug-in configuration data includes:

6. The method for installing a plug-in according to claim 5, wherein the step of installing the plug-in file according to the installation manner comprises:

7. A method of installing a card, the method comprising:

8. An insert mounting apparatus, comprising:

9. An installation apparatus of a plug-in, characterized in that the installation apparatus of the plug-in comprises a memory, a processor and an installation program of the plug-in stored on the memory and executable on the processor, the installation program of the plug-in realizing the steps of the installation method of the plug-in as claimed in any one of claims 1 to 6 when executed by the processor.

10. A computer-readable storage medium, having stored thereon an installer for a plug-in, the installer for the plug-in, when executed by a processor, implementing the steps of the method for installing a plug-in according to any of claims 1 to 6.