An application plug-in compatible processing method and device

Abstract

The application provides an application plug-in compatibility processing method and device, wherein the method comprises the following steps: obtaining a routing identifier of a target page; obtaining host plug-in data corresponding to the target page and routing plug-in data by using a preset routing framework according to the routing identifier of the target page, wherein the host plug-in data is plug-in resources pre-installed in a host; and loading the target page by using the host plug-in data in response to the routing plug-in data failing to be obtained or in response to the routing plug-in data not satisfying a preset plug-in jump condition. Therefore, the embodiments of the application can ensure that the software functions are normal and the function pages are stable and available by loading the target page based on the plug-in resources pre-installed in the host in the case that the routing plug-in data fails to be obtained or does not satisfy the jump condition.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of application program plug-in compatibility processing method and device. BACKGROUND

[0002] Android application updates often need to download and install the entire application package on the user side, and the installation interface needs to be forcibly popped up during installation, which is not user-friendly, resulting in users ignoring upgrades and low software update rates.

[0003] In the prior art, business modules can be plug-in processed based on an open-source plug-in framework, enabling silent installation of application programs without user-side pop-up windows. However, since plug-in relies on the hook mechanism to achieve dynamic loading of plug-in module code, and there are many existing API versions in the Android system, which need to be compatible with various framework layer codes, plug-in technology generally fails to upgrade or run, resulting in software functionality being unavailable and poor stability. Therefore, there is an urgent need for an application program plug-in compatibility processing method that can ensure software functionality and functional pages are stable and available in the event of plug-in upgrade or runtime failure. SUMMARY

[0004] Therefore, the present application provides an application program plug-in compatibility processing method and device that can ensure software functionality and functional pages are stable and available in the event of plug-in upgrade or runtime failure.

[0005] The technical solution is as follows:

[0006] In a first aspect, the present application embodiment provides an application program plug-in compatibility processing method, which comprises:

[0007] obtaining a routing identifier of a target page;

[0008] According to the routing identifier of the target page, using a preset routing framework to obtain host plug-in data and routing plug-in data corresponding to the target page, wherein the host plug-in data is a plug-in resource pre-installed in the host;

[0009] In response to the routing plug-in data failing to be obtained, or in response to the routing plug-in data not meeting a preset plug-in jump condition, loading the target page using the host plug-in data.

[0010] Optionally, before obtaining the routing identifier of the target page, the method further comprises:

[0011] dividing a target application program into at least one business module, wherein the business module comprises at least one page;

[0012] encapsulating the business module as a plug-in resource, wherein the business module corresponds to the plug-in resource one by one.

[0013] Optionally, the obtaining, according to the route identifier of the target page, of the host plug-in data and the route plug-in data corresponding to the target page by using a preset route framework comprises:

[0014] obtaining, according to the route identifier of the target page, of the host plug-in data corresponding to the target page and pre-installed on a host by using a preset host route framework, the host plug-in data comprising a version number and running information of a host plug-in;

[0015] obtaining, according to the route identifier of the target page, of the route plug-in data corresponding to the target page by using a preset plug-in route framework, the route plug-in data comprising a version number and running information of a route plug-in.

[0016] Optionally, the determining that the route plug-in data does not satisfy a preset plug-in jump condition comprises: when the version number of the host plug-in is greater than or equal to the version number of the route plug-in, and / or when the running information of the route plug-in is disabled, determining that the route plug-in data does not satisfy the preset plug-in jump condition.

[0017] Optionally, the method further comprises:

[0018] loading the target page by using the route plug-in data in response to the running information of the host plug-in being disabled, or in response to the route plug-in data satisfying a preset plug-in jump condition, wherein the response to the route plug-in data satisfying the preset plug-in jump condition comprises: when the version number of the route plug-in is greater than the version number of the host plug-in, and when the running information of the route plug-in is enabled, determining that the route plug-in data satisfies the preset plug-in jump condition.

[0019] In a second aspect, an application program plug-in compatible processing device is provided, and the device comprises:

[0020] an obtaining module configured to obtain a route identifier of a target page;

[0021] The obtaining module is further configured to obtain, according to the route identifier of the target page, host plug-in data and route plug-in data corresponding to the target page by using a preset route framework, wherein the host plug-in data is a plug-in resource pre-installed on a host.

[0022] The loading module is configured to load the target page by using the host plug-in data in response to the route plug-in data acquisition failure or in response to the route plug-in data not meeting preset plug-in jump conditions.

[0023] Optionally, the apparatus further comprises:

[0024] The splitting module is configured to split the target application into at least one business module, wherein the business module comprises at least one page.

[0025] The encapsulating module is configured to encapsulate the business module into a plug-in resource, wherein the business module and the plug-in resource correspond to each other.

[0026] Optionally, the obtaining module comprises:

[0027] The host plug-in obtaining submodule is configured to obtain, according to a route identifier of the target page, host plug-in data corresponding to the target page and pre-installed on a host by using a preset host route framework, wherein the host plug-in data comprises a version number and running information of the host plug-in.

[0028] The route plug-in obtaining submodule is configured to obtain, according to the route identifier of the target page, route plug-in data corresponding to the target page by using a preset plug-in route framework, wherein the route plug-in data comprises a version number and running information of the route plug-in.

[0029] Optionally, the loading module in response to the route plug-in data not meeting preset plug-in jump conditions comprises: when the version number of the host plug-in is greater than or equal to the version number of the route plug-in, and / or when the running information of the route plug-in is disabled, determining that the route plug-in data does not meet preset plug-in jump conditions.

[0030] Optionally, the loading module is further configured to:

[0031] In response to the running information of the host plug-in being disabled or in response to the route plug-in data meeting preset plug-in jump conditions, the loading module is configured to load the target page by using the route plug-in data, wherein the response to the route plug-in data meeting preset plug-in jump conditions comprises: when the version number of the route plug-in is greater than the version number of the host plug-in, and when the running information of the route plug-in is allowed to be used, determining that the route plug-in data meets preset plug-in jump conditions.

[0032] The above technical solution has the following beneficial effects:

[0033] The application embodiment provides an application plug-in compatible processing method, when the method is executed, a route identifier of a target page is acquired; according to the route identifier of the target page, a preset route framework is used to acquire host plug-in data and route plug-in data corresponding to the target page, wherein the host plug-in data is plug-in resource pre-installed in a host; when the route plug-in data fails to be acquired, or when the route plug-in data does not meet preset plug-in jump conditions, the target page is loaded by using the host plug-in data. Therefore, the application embodiment can realize loading of the target page based on the plug-in resource pre-installed in the host in the case that the route plug-in data fails to be acquired or does not meet the jump conditions, so as to ensure normal software functions and stable and available function pages.

[0034] The application embodiment also provides a device corresponding to the above method, which has the same beneficial effects as the above method. BRIEF DESCRIPTION OF DRAWINGS

[0035] In order to more clearly illustrate the technical solutions in the application embodiments or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or the prior art description. Obviously, the drawings in the following description are only some embodiments of the application, and for those skilled in the art, other drawings can be obtained without creative labor based on the provided drawings.

[0036] Figure 1 A flowchart of an application plug-in processing provided by the application embodiment;

[0037] Figure 2 A flowchart of an application plug-in compatible processing method provided by the application embodiment;

[0038] Figure 3 A structural diagram of an application plug-in compatible processing device provided by the application embodiment. DETAILED DESCRIPTION

[0039] The technical solutions in the application embodiments will be described clearly and completely in combination with the drawings in the application embodiments. Obviously, the described embodiments are only some of the embodiments of the application, not all the embodiments. Based on the embodiments in the application, all other embodiments obtained by those skilled in the art without creative labor are within the protection scope of the application.

[0040] As Figure 1A flowchart of application plug-in processing is shown, and an Android application is divided into multiple business modules according to business functions, such as a network business module WebPrj, a video on demand business module VodPrj, and a payment business module PayPrj. The codes of each business module are encapsulated to obtain plug-ins APK1, APK2, and APK3 of the application. The business module and the plug-in are one-to-one corresponding. The host terminal includes the codes of all business modules. The plug-in APK can be upgraded to the host terminal in silence through the plug-in technology. However, due to compatibility and other problems, the plug-in technology may fail to upgrade or run the plug-in, thereby causing the software function to be unavailable and the stability to be poor.

[0041] In order to ensure the normal software function and the stable and available function page in the case of plug-in upgrade failure or running failure, an application plug-in compatibility processing method is provided in the embodiments of the present application. Please refer to Figure 2 The method can include the following steps.

[0042] Step S100: Obtain a routing identifier of a target page.

[0043] Specifically, the target page can be any page of any business module in the application program. The application program includes at least one business module, and one business module includes at least one page. The routing identifier is used to identify the target page. As an option, the routing identifier can be a uniform resource identifier (URI). It can be understood that the routing identifier can also be other symbols, characters, or strings used to uniquely identify the target page.

[0044] In an optional embodiment, the embodiments of the present application can further include, before step S100: dividing a target application into at least one business module, and encapsulating the business module as a plug-in resource, wherein the business module includes at least one page, and the business module and the plug-in resource are one-to-one corresponding.

[0045] Specifically, the target application is divided into at least one business module according to business functions, and the business module is encapsulated to obtain a plug-in resource of the target application. One business module includes at least one page, and the business module and the plug-in resource are one-to-one corresponding, that is, one business module corresponds to one plug-in.

[0046] Step S200: According to the routing identifier of the target page, obtain the host plug-in data and the routing plug-in data corresponding to the target page by using a preset routing framework.

[0047] Specifically, the preset routing framework is used to implement mapping of the routing identifier and the plug-in resource, and the routing identifier corresponding to each page of the business module is registered in the host terminal. The host application program can identify the routing identifier through the routing framework. Then, the host terminal can acquire the host plug-in resource and the routing plug-in resource corresponding to the target page according to the routing identifier by using the preset routing framework, wherein the host plug-in data refers to the plug-in resource pre-installed in the host, and the routing plug-in resource refers to the plug-in resource obtained after the application program is plug-inized.

[0048] In an alternative embodiment, the step S200 of the embodiment of the application can include the following steps:

[0049] Step S201: acquiring, according to the routing identifier of the target page, the host plug-in data pre-installed in the host and corresponding to the target page by using the preset host routing framework.

[0050] Step S202: acquiring, according to the routing identifier of the target page, the routing plug-in data corresponding to the target page by using the preset plug-in routing framework.

[0051] Specifically, the routing framework is used to implement mapping of the routing identifier and the plug-in resource. In the plug-inization of the application program, the code reuse of the plug-in and the business module both include the routing framework. The routing framework in the host code is referred to as the host routing framework. According to the routing identifier of the target page, the host plug-in data corresponding to the target page can be acquired through the host routing framework. The host plug-in data can include the version number, running information, plug-in name, activity and other information of the host plug-in.

[0052] The routing framework in the plug-in code is referred to as the plug-in routing framework. According to the routing identifier of the target page, the routing plug-in data corresponding to the target page can be acquired through the plug-in routing framework. The routing plug-in data includes the version number, running information, plug-in name, activity and other information of the routing plug-in.

[0053] It should be noted that the host terminal can include a jump module. The jump module acquires the plug-in data corresponding to the routing identifier on the host terminal through the reflection (Reflection) mechanism and the annotation (Annotation) technology of JAVA.

[0054] The reflection mechanism of JAVA is a feature of JAVA, which refers to constructing and calling an object of any class and calling the attributes and methods of any object according to the path of the class in the running state of the program. In the embodiment of the application, the reflection mechanism of JAVA is specifically applied as follows: because the host terminal cannot directly call the class of the plug-in in the code, the class and method of the plug-in can be acquired and called by reflection, and the plug-in name and plug-in version information corresponding in the plug-in can be acquired.

[0055] Annotate, also known as metadata, a code level description, is a feature introduced in JDK1.5 and later versions, which can be declared in front of packages, classes, fields, methods, local variables, method parameters, etc. to describe these elements. In the embodiment of the application, the annotation technology is specifically applied to: defining an annotation class to identify all page corresponding route identifiers, and then in the code, the route identifier and the path of the corresponding page Activity class can be obtained through the API related to the annotation technology.

[0056] Step S300: in response to the failure of the route plug-in data acquisition, or in response to the route plug-in data not meeting the preset plug-in jump condition, loading the target page by using the host plug-in data.

[0057] Specifically, in the case of failure of the route plug-in data acquisition, or in the case of the acquired route plug-in data not meeting the preset plug-in jump condition, the target page can be loaded based on the acquired host plug-in data. It can be understood that in the case of failure of the route plug-in data acquisition or not meeting the preset condition, the host terminal can load the target page based on the plug-in resource of the host installed in advance to ensure the normal software function and stable and available function page.

[0058] In an optional embodiment, in step S300 of the embodiment, in response to the route plug-in data not meeting the preset plug-in jump condition, it can include: when the version number of the host plug-in is greater than or equal to the version number of the route plug-in, and / or when the running information of the route plug-in is disabled, it is determined that the route plug-in data does not meet the preset plug-in jump condition.

[0059] Specifically, when the version number of the host plug-in is greater than or equal to the version number of the route plug-in, for example, the version number of the host plug-in is 2.0, the version number of the route plug-in is 1.0, and / or when the running information of the route plug-in is disabled, it is determined that the route plug-in data does not meet the preset plug-in jump condition.

[0060] In an optional embodiment, the embodiment can further include:

[0061] In response to the running information of the host plug-in being disabled, or in response to the route plug-in data meeting the preset plug-in jump condition, loading the target page by using the route plug-in data, wherein in response to the route plug-in data meeting the preset plug-in jump condition includes: when the version number of the route plug-in is greater than the version number of the host plug-in, and when the running information of the route plug-in is allowed to be used, it is determined that the route plug-in data meets the preset plug-in jump condition.

[0062] Specifically, when the running information of the host plug-in is disabled, or when the routing plug-in data meets the preset plug-in jump condition, the target page is loaded by using the routing plug-in data. Wherein, the routing plug-in data meets the preset plug-in jump condition includes: when the version number of the routing plug-in is greater than the version number of the host plug-in, for example: the version number of the routing plug-in is 2.0, the version number of the host plug-in is 1.0, and the running information of the routing plug-in is allowed to be used, it is determined that the routing plug-in data meets the preset plug-in jump condition.

[0063] In an optional implementation, the embodiment can further include: in response to failure of loading the target page by using the routing plug-in data, loading the target page by using the host plug-in data.

[0064] Specifically, when the loading of the target page by using the routing plug-in data fails, the jump to the target page is implemented by using the host plug-in data, so as to ensure the normal display of the function page.

[0065] It should be noted that if the loading of the target page by using the host plug-in data also fails, the host home page can be jumped to, so as to avoid the software page from being dead, and ensure the normal display of the page.

[0066] In an optional implementation, the embodiment can further include: in response to failure of loading the target page by using the routing plug-in data, setting the running information of the routing plug-in as disabled, so as to avoid the subsequent host from loading the routing plug-in data, and causing the resource occupation.

[0067] In summary, the embodiment of the present application provides an application plug-in compatible processing method, when the method is executed, the routing identifier of a target page is acquired; according to the routing identifier of the target page, the host plug-in data and the routing plug-in data corresponding to the target page are acquired by using a preset routing framework, wherein the host plug-in data is a plug-in resource pre-installed in a host; in response to failure of acquiring the routing plug-in data, or in response to the routing plug-in data not meeting a preset plug-in jump condition, the target page is loaded by using the host plug-in data. It can be known that in the case that the routing plug-in data fails to be acquired or does not meet the jump condition, the loading of the target page is implemented based on the plug-in resource pre-installed in the host, so as to ensure the normal software function and the stable and available function page.

[0068] Corresponding to the above method, the embodiment of the present application further provides an application plug-in compatible processing device, please refer to Figure 3 , a structural schematic diagram of the device is shown, the device can include:

[0069] The acquisition module 301 is configured to acquire the routing identifier of a target page.

[0070] The acquisition module 301 is further configured to acquire, according to a routing identifier of the target page, host plug-in data corresponding to the target page and routing plug-in data by using a preset routing framework, wherein the host plug-in data is plug-in resource pre-installed on a host.

[0071] The loading module 302 is configured to load the target page by using the host plug-in data, in response to the routing plug-in data acquisition failing, or in response to the routing plug-in data not satisfying a preset plug-in jump condition.

[0072] In an optional implementation, the apparatus can further include:

[0073] The splitting module is configured to divide a target application into at least one business module, wherein the business module includes at least one page.

[0074] The encapsulating module is configured to encapsulate the business module as plug-in resource, wherein the business module and the plug-in resource correspond to each other.

[0075] In an optional implementation, the acquisition module 301 includes:

[0076] The host plug-in acquisition submodule is configured to acquire, according to a routing identifier of the target page, host plug-in data corresponding to the target page pre-installed on the host by using a preset host routing framework, wherein the host plug-in data includes a version number and running information of the host plug-in.

[0077] The routing plug-in acquisition submodule is configured to acquire, according to the routing identifier of the target page, routing plug-in data corresponding to the target page by using a preset plug-in routing framework, wherein the routing plug-in data includes a version number and running information of the routing plug-in.

[0078] In an optional implementation, the loading module, in response to the routing plug-in data not satisfying a preset plug-in jump condition, includes: when the version number of the host plug-in is greater than or equal to the version number of the routing plug-in, and / or when the running information of the routing plug-in is disabled, determining that the routing plug-in data does not satisfy the preset plug-in jump condition.

[0079] In an optional implementation, the loading module 302 is further configured to:

[0080] In response to the running information of the host plug-in being disabled, or in response to the route plug-in data satisfying a preset plug-in jump condition, the target page is loaded using the route plug-in data, wherein the response to the route plug-in data satisfying the preset plug-in jump condition comprises: when the version number of the route plug-in is greater than the version number of the host plug-in, and when the running information of the route plug-in is allowed to be used, it is determined that the route plug-in data satisfies the preset plug-in jump condition.

[0081] In an optional implementation, the loading module 302 is further configured to load the target page using the host plug-in data in response to failure of loading the target page using the route plug-in data.

[0082] In an optional implementation, the apparatus can further include:

[0083] In an optional implementation, the apparatus can further include:

[0084] It should be noted that the steps performed by each module in the application embodiment of the application and the related technical features correspond to the method provided by the application embodiment, and the description of the device part can be referred to the foregoing method part, and details are not described herein.

[0085] In summary, the application embodiment provides an application program plug-in compatible processing apparatus, which includes: an acquisition module configured to acquire a route identifier of a target page; the acquisition module is further configured to acquire host plug-in data and route plug-in data corresponding to the target page using a preset route framework according to the route identifier of the target page, wherein the host plug-in data is plug-in resources pre-installed in a host; and a loading module configured to load the target page using the host plug-in data in response to failure of acquiring the route plug-in data, or in response to the route plug-in data not satisfying a preset plug-in jump condition. Therefore, the application embodiment can load the target page based on the plug-in resources pre-installed in the host in the case of failure of acquiring the route plug-in data or not satisfying the jump condition, so as to ensure normal software function and stable and available function page.

[0086] Each embodiment in the specification is described in a progressive manner, and each embodiment focuses on the difference from other embodiments, and the same or similar parts between each embodiment can be referred to each other.

[0087] Those skilled in the art can understand that the flowchart shown in the figure is only an example in which the embodiments of the application can be implemented, and the application scope of the embodiments of the application is not limited by any aspect of the flowchart.

[0088] In several embodiments provided in the present application, it should be understood that the disclosed methods, devices and equipment can be implemented in other ways. For example, the above-described device embodiments are only illustrative, and for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some communication interfaces, devices or units, which can be electrical, mechanical or other forms.

[0089] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, i.e., they can be located in one place or distributed on multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiment scheme according to actual needs. In addition, the functional units in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present alone, or two or more units can be integrated in one unit.

[0090] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the part of the technical solutions that essentially contribute to the prior art can be embodied in the form of a software product, which is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

[0091] The above description of the disclosed embodiments enables a person skilled in the art to implement or use the present application. Various modifications to the embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An application plug-in compatibility processing method, characterized by, The method comprises: obtaining a routing identifier of a target page; obtaining host plug-in data and routing plug-in data corresponding to the target page by using a preset routing framework according to the routing identifier of the target page, wherein the host plug-in data is plug-in resource pre-installed on a host, and the routing plug-in resource is plug-in resource obtained after application plug-in processing; loading the target page by using the host plug-in data in response to failure in obtaining the routing plug-in data or in response to the routing plug-in data not satisfying a preset plug-in jump condition.

2. The method of claim 1, wherein, Before the obtaining of the routing identifier of the target page, the method further comprises: dividing a target application program into at least one business module, wherein the business module comprises at least one page; encapsulating the business module as plug-in resource, wherein the business module and the plug-in resource correspond to each other.

3. The method of claim 1, wherein, The obtaining of the host plug-in data and the routing plug-in data corresponding to the target page by using the preset routing framework according to the routing identifier of the target page comprises: obtaining host plug-in data pre-installed on the host corresponding to the target page by using a preset host routing framework according to the routing identifier of the target page, wherein the host plug-in data comprises a version number and running information of the host plug-in; obtaining routing plug-in data corresponding to the target page by using a preset plug-in routing framework according to the routing identifier of the target page, wherein the routing plug-in data comprises a version number and running information of the routing plug-in.

4. The method of claim 3, wherein, The determining of the routing plug-in data not satisfying the preset plug-in jump condition in response to the routing plug-in data not satisfying the preset plug-in jump condition comprises: determining that the routing plug-in data does not satisfy the preset plug-in jump condition when the version number of the host plug-in is greater than or equal to the version number of the routing plug-in and / or when the running information of the routing plug-in is disabled.

5. The method of claim 4, wherein, The method further comprises: loading the target page by using the routing plug-in data in response to the running information of the host plug-in being disabled or in response to the routing plug-in data satisfying the preset plug-in jump condition, wherein the determining of the routing plug-in data satisfying the preset plug-in jump condition in response to the routing plug-in data satisfying the preset plug-in jump condition comprises: determining that the routing plug-in data satisfies the preset plug-in jump condition when the version number of the routing plug-in is greater than the version number of the host plug-in and when the running information of the routing plug-in is enabled.

6. An application plug-in compatibility processing apparatus characterized by comprising: The apparatus comprises: an obtaining module configured to obtain a routing identifier of a target page; the obtaining module is further configured to obtain host plug-in data and routing plug-in data corresponding to the target page by using a preset routing framework according to the routing identifier of the target page, wherein the host plug-in data is plug-in resource pre-installed on a host, and the routing plug-in resource is plug-in resource obtained after application plug-in processing; a loading module configured to load the target page by using the host plug-in data in response to failure in obtaining the routing plug-in data or in response to the routing plug-in data not satisfying a preset plug-in jump condition.

7. The apparatus of claim 6, wherein, The apparatus further comprises: The splitting module is configured to divide the target application into at least one business module, wherein the business module includes at least one page. The packaging module is configured to package the business module as a plug-in resource, wherein the business module corresponds to the plug-in resource one by one.

8. The apparatus of claim 6, wherein, The obtaining module includes: The host plug-in obtaining sub-module is configured to obtain, according to the routing identifier of the target page, host plug-in data corresponding to the target page from a preset host routing framework, wherein the host plug-in data includes a version number and running information of the host plug-in. The routing plug-in obtaining sub-module is configured to obtain, according to the routing identifier of the target page, routing plug-in data corresponding to the target page from a preset plug-in routing framework, wherein the routing plug-in data includes a version number and running information of the routing plug-in.

9. The apparatus of claim 8, wherein, The loading module determines that the routing plug-in data does not satisfy the preset plug-in jump condition when the version number of the host plug-in is greater than or equal to the version number of the routing plug-in, and / or when the running information of the routing plug-in is disabled.

10. The apparatus of claim 9, wherein, The loading module is further configured to: When the running information of the host plug-in is disabled, or when the routing plug-in data satisfies the preset plug-in jump condition, the loading module loads the target page by using the routing plug-in data, wherein the loading module determines that the routing plug-in data satisfies the preset plug-in jump condition when the version number of the routing plug-in is greater than the version number of the host plug-in, and when the running information of the routing plug-in is enabled.

Images