CN107832099B - A client version compatible method, device and storage medium - Google Patents

Abstract

The invention discloses a method for client version compatibility. The method includes: receiving a loading request of a World Wide Web page sent by a current client; Whether the version of the client side matches, generate a detection result; when the detection result indicates that the version of the web page to be called is higher than the version of the current client, intercept and use the method agreed in the JSBridge protocol of the historical version compatible with the current client. call the web page; obtain the target calling method for calling the web page corresponding to the method agreed in the historical version JSBridge protocol from the compatible code base; call the web page according to the target calling method, Causes the web page to be displayed on the current client. The invention also provides a client version compatible device and storage medium.

Description

A client version compatible method, device and storage medium

technical field

The present invention relates to page display technology, and in particular, to a client version compatible method, device and storage medium.

Background technique

With the continuous development of Internet information technology, more and more smart terminals have been developed and widely used in all aspects of life. For example, the smart terminals mentioned here can be desktop computers, notebook computers, smart phones, tablet computers, Smart watches, etc., and applications (Application, APP) that can be installed on these smart terminals can be further classified into native (native) applications, World Wide Web (web, World Wide Web) applications, and hybrid applications.

Among them, the native applications are specially developed for a certain type of intelligent terminal, and they can directly run on the operating system of the corresponding intelligent terminal. For example, an application developed for the iOS operating system or an application developed for the Android operating system.

In simple terms, web applications can refer to applications designed and developed based on browsers. They can be run using browsers on smart terminals (such as IE in Windows systems and Safari in iPhones), and they can run in various different running on the operating system.

The hybrid application (hybird APP), as the name suggests, refers to the combination of native application and web application, using part of native application and part of web application. Since hybrid applications have both the advantages of good user interaction experience of native applications and the advantages of cross-platform development of web applications, some mainstream applications are now being developed in the direction of hybrid applications.

In order to realize the mutual call between the web application part and the native application part in the hybrid application, it is necessary to develop the JSBridge protocol as a communication bridge between the wen application part and the native application part in the existing technology. Through the JSBridge protocol, the native application of the hybrid application can be made The part calls the js code of the web application part, or also allows the web application part to "call" the code of the native application part.

However, in the existing hybrid applications, due to the characteristics of the web application part, developers often update the web application part in the hybrid application, while the update frequency for the native application part is often low, so it often occurs in actual use. The following situations:

In the hybrid application used by the user, the native application part is the historical version (that is, the client installed on the mobile phone is the historical version client), and the web application part is the updated new version. When updating the web application part, new web pages may be developed according to the html5 protocol predetermined by the latest standard. For newly developed web pages, they often need to be called according to the new version of the JSBridge protocol, and because the client (native application) Some) versions have not been updated, so the new version of the JSBridge protocol may not be integrated on the client of the historical version, so when the web application part of the hybrid application is updated, the client of the historical version (native application part) may not be able to call the new version The user can only update the historical version client (native application part) to solve the above problems. It can be seen that in the existing hybrid application, in order to solve the historical version client (native application part) and new The problem of incompatibility of the version web pages is to integrate the historical version JSBridge protocol compatible with the historical version client in the new version page for various historical version clients, or the user needs to update the historical version client. In this way, it not only consumes the user's time, but also causes the user to be unable to use the application of the new version of the page when the update is not timely, which in turn has a great impact on the normal use of the user.

SUMMARY OF THE INVENTION

In order to solve the above technical problems, the embodiments of the present invention provide a client version compatible method, device and storage medium, which can solve the problem caused by the incompatibility between the version of the client and the version of the called page in the existing hybrid application. The problem of not being able to display the new page.

The technical solution of the embodiment of the present invention is realized as follows:

According to an aspect of the embodiments of the present invention, a method for client version compatibility is provided, and the method includes:

Receive the loading request of the World Wide Web page sent by the current client;

According to the loading request of the web page, detect whether the version of the web page to be called matches the version of the current client, and generate a detection result;

When the detection result indicates that the version of the web page to be called is higher than the version of the current client, intercepting and using the method agreed in the JSBridge protocol of the historical version compatible with the current client to call the web page;

Obtain from the compatible code base the target invocation method for invoking the web page corresponding to the method agreed in the historical version JSBridge protocol;

The web page is invoked according to the target invocation method, so that the web page is displayed on the current client.

In the above scheme, the method also includes:

When the detection result indicates that the version of the web page to be invoked is lower than the version of the current client, the web page is invoked according to the method agreed in the JSBridge protocol of the historical version.

In the above scheme, the method also includes:

When the detection result indicates that the version of the web page to be called is the version of the newly added page, a message for prompting the user to update the version of the current client is output.

In the above solution, when the detection result indicates that the version of the web page to be called is higher than the version of the current client, the method further includes:

sending a load request to load the compatible code base;

When the loading request is successfully responded, the compatible code base is loaded, so that the target calling method for calling the web page corresponding to the method agreed in the JSBridge protocol of the historical version is obtained from the compatible code base.

In the above scheme, the method also includes:

After the web page is successfully called according to the target calling method, the compatible code base is uninstalled, so that the storage space of the current client occupied by the compatible code base is released.

According to another aspect of the embodiments of the present invention, a client version compatible device is provided, the device includes: a receiving unit, a detecting unit, an intercepting unit, an acquiring unit, and a calling unit;

Wherein, the receiving unit is used to receive the loading request of the World Wide Web page sent by the current client;

The detection unit is configured to, according to the loading request of the web page, detect whether the version of the web page to be called matches the version of the current client, and generate a detection result;

The intercepting unit is configured to intercept, when the detection result indicates that the version of the web page to be called is higher than the version of the current client, intercept the web page using the method agreed in the JSBridge protocol of the historical version compatible with the current client. page to call;

The obtaining unit is used to obtain the target calling method of calling the web page corresponding to the method agreed in the historical version JSBridge protocol from the compatible code base;

The calling unit is configured to call the web page according to the target calling method, so that the web page is displayed on the current client.

In the above solution, the invoking unit is further configured to invoke the web page according to the method agreed in the JSBridge protocol of the historical version when the detection result indicates that the version of the web page to be invoked is lower than the version of the current client. page.

In the above solution, the device further comprises: an output unit,

The output unit is configured to output a message for prompting the user to update the version of the current client when the detection result indicates that the version of the web page to be called is the version of the newly added page.

In the above solution, the device further includes: a sending unit and a loading unit;

the sending unit, configured to send a loading request for loading the compatible code base when the detection result indicates that the version of the web page to be called is higher than the version of the current client;

The loading unit is used to load the compatible code base when the load request is successfully responded, so that the web page corresponding to the method agreed in the historical version JSBridge protocol is obtained from the compatible code base The target calls the method.

In the above solution, the device further comprises: an unloading unit;

The unloading unit is configured to unload the compatible code base after successfully calling the web page according to the target calling method, so that the storage space of the current client occupied by the compatible code base is released.

According to yet another aspect of the embodiments of the present invention, there is provided a client version compatible device, the device comprising: a memory and a processor;

Wherein, the memory is used to store a computer program that can run on the processor;

The processor, when running the computer program, executes the steps of any one of the above methods that are compatible with client versions.

According to yet another aspect of the embodiments of the present invention, a computer-readable storage medium is provided on which a computer program is stored, and when the computer program is executed by a processor, any one of the foregoing methods for client version compatibility is implemented the steps of the method.

In the technical solution of the embodiment of the present invention, a method, device and storage medium compatible with client versions are provided. By receiving a loading request of a World Wide Web page sent by a current client; Whether the version of the web page of the current client matches the version of the current client, a detection result is generated; when the detection result indicates that the version of the web page to be called is higher than the version of the current client, intercept and use the historical version compatible with the current client The web page is called by the method agreed in the JSBridge protocol; the target invocation method for calling the web page corresponding to the method agreed in the historical version of the JSBridge protocol is obtained from the compatible code base; the method is invoked according to the target the web page, so that the web page is displayed on the current client. In this way, it is not necessary to integrate the "historical version JSBridge protocol" compatible with the historical version clients for various historical version clients on the new version page, and the user does not need to update the historical version clients. Greatly improve the user experience.

Description of drawings

FIG. 1 is a schematic flowchart of a method for client version compatibility according to an embodiment of the present invention;

2 is a schematic diagram of an interaction flow between a client and a web page to be called in an embodiment of the present invention;

3 is a schematic structural composition diagram of a client version compatible device in an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a client version compatible device according to another embodiment of the present invention.

Detailed ways

The specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only used to illustrate and explain the present invention, but not to limit the present invention.

FIG. 1 is a schematic flowchart of a method for client version compatibility according to an embodiment of the present invention; as shown in FIG. 1 , the method includes:

Step 101, receiving the loading request of the web page sent by the current client;

In the embodiment of the present invention, the method is mainly applied to a Hybrid App (mixed-mode mobile application), and the Hybrid App is usually installed on terminals such as desktop computers, notebook computers, smart phones, tablet computers, and smart watches.

Specifically, the Hybrid App refers to an APP between the WEB-APP and the Native-APP, and has both the "advantage of a good user interaction experience of the Native App" and the "advantage of the cross-platform development of the Web App".

Below, take the mobile APP as an example:

Native applications include: Kugou Music, Meitu Xiuxiu, such APPs can be called native applications;

Web applications include: ticket grabbing assistant and recharge easily opened through UC browser, these are web applications;

Hybrid applications include: Tmall, Ctrip, and 58.com. Most of them wrap web pages on the basis of native applications, such as 58.com's posts, Tmall's event pages, and Ctrip's order details pages. Embedding web pages to achieve search.

Take the PC APP as an example:

Native applications include: such as QQ, Thunder, etc.;

Web applications include: such as the once-popular web games;

Hybrid applications include: such as 360 mobile phone assistant.

When a user wants to perform an opening operation on an object in the current client, it can be implemented by sending a web page loading request to the client.

For example, when the user wants to adjust the "recharge center" application in the hybrid application "Alipay", by touching the icon corresponding to the "recharge center" with a finger, the user can send a message with the "recharge center" to the client. "The loading request of the corresponding web page, so that the client receives the loading request of the web page.

Step 102, according to the loading request of the web page, detect whether the version of the web page to be called matches the version of the current client, and generate a detection result;

In the embodiment of the present invention, after the client receives the loading request of the web page, the web application part in the hybrid application does not directly call the code of the native application part, but can be based on the web application part and the native application part. The rules agreed in the application part notify the native application part of what needs to be done through the JSBridge protocol, and then the native application part can execute the corresponding code. In the same way, the native application part in the hybrid application does not directly call the code of the web application part, but can notify the web application part of what needs to be done through the JSBridge protocol according to the rules agreed between the web application part and the native application part, and then The web application part can execute the corresponding code.

Here, JSBridge is the communication bridge between Native code and JS code, because the communication between JS and Native must be realized through an H5 global object JSBridge, and the object name is "JSBridge", which is the global object window in the H5 page an attribute of . Therefore, in this embodiment of the present invention, when the native application executes the code that invokes the web application part, the client needs to detect whether the version of the web page to be invoked matches the version of the current client, and obtain the detection result. When the detection result indicates that the version of the web page to be invoked matches the version of the current client, the web page is invoked according to the page invocation method agreed upon in the JSBridge protocol. When the detection result indicates that the version of the web page to be called does not match the version of the current client, step 103 is performed.

It should be noted that when the developer updates the current client or the web page in the current client, after the update, the current client or web page will be marked with a specific identifier (such as a version number) at the same time, and then when the local client When the client needs to call a certain web page in the client, the current client can judge the version of the client and the version of the web page to be called by comparing whether the version number of the web page to be called matches the current client version number match.

For example, if the developer develops a corresponding web page for the client of version 1.0 installed on the current terminal, and the version number of the web page is 2.1, when the user uses the client of version 1.0 to call the web page of version 2.1 later , the client of version 1.0 determines that the current version of the client of version 1.0 matches the version of the web page of version 2.1 to be called.

Step 103, when the detection result represents that the version of the web page to be invoked is higher than the version of the current client, intercept and use the method agreed in the JSBridge protocol of the historical version compatible with the current client to invoke the web page;

In this embodiment of the present invention, when the current client does not match the version of the web page to be called, at least one of the following situations is included:

Case 1: The current client detects that the version of the web page to be called is higher than the version of the current client. That is to say, the version of the current client is lower than the version of the web page to be called, that is, the old client calls the new page;

At this time, the current client calls the web page according to the method agreed in the JSBridge protocol of the historical version.

In this embodiment of the present invention, when the version of the web page to be called is higher than the version of the current client, at least one of the following scenarios is included, wherein:

Scenario 1: The new version page is obtained after updating the historical version page that can be called by the historical version client;

In this case, the historical version client itself saves the method for calling the historical version page, so the compatible code base can be loaded according to the method used to call the historical version page, and the compatible code base can be found for calling The method of the new version page, and call the new version page through the found method for calling the new version page.

Here, when loading the compatible code base, specifically, the current client may send a loading request for loading the compatible code base to the background server of the client; when the loading request is successfully responded by the background server, the compatible code base is called. The code base is loaded, and the compatible code base is loaded, so that the target calling method for calling the web page corresponding to the method agreed in the JSBridge protocol of the historical version can be obtained from the compatible code base. A specific interaction flow between the client and the web page to be called is shown in FIG. 2 .

Fig. 2 is the schematic diagram of the interaction flow between the client and the web page to be called in the embodiment of the present invention; as shown in Fig. 2:

Assuming that both the client before the update and the web page to be called are version 1.0, and the client and the web page use the 1.0 version of the JSBridge protocol to call each other, according to the 1.0 version of the JSBridge protocol, the The client can use method A to call the web page of version 1.0, and after the update, the web page is updated to version 2.0. When the user needs to call the web page of version 2.0 at this time, it needs to follow the 2.0 version of the JSBridge protocol agreement In this case, when the client of version 1.0 calls the web page of version 2.0 through method A, the underlying basic library loaded by the client will intercept the client of version 1.0 through method A. Call, and through the compatible code base, find the B method corresponding to the A method and used to call the 2.0 version of the web page, and then use the determined B method to call the 2.0 version of the web page.

The above invocation method avoids the problem of error reporting when the client invokes the web page due to incompatible versions between the client and the web page to be invoked.

Scenario 2: The new version page that the historical version client needs to call is the newly added page;

In this case, since the new version page is a newly added page, there is no historical version page corresponding to the new version page, so the historical version client itself does not save the method for calling the page, so Also, the method for calling the new version page cannot be found from the compatible code base, and at this time, the client outputs a message for prompting the user to update the version of the current client.

The prompting method may be a voice prompt, or a pop-up "update window" on the display interface of the current client, or a prompt in the form of text characters.

Case 2: The version of the current client is higher than the version of the web page to be called, that is, the new client calls the old page;

In the case where the new client calls the old page, it is assumed that the new version client still has the page calling method according to the historical version of the JSBridge protocol. In this case, the new version of the client can directly use the historical version of the JSBridge protocol. The page call method of the page calls the historical version web page.

Step 104, obtain the target calling method of calling the web page corresponding to the method agreed in the historical version JSBridge protocol from the compatible code base;

In the embodiment of the present invention, when the new version client does not store the page calling method according to the historical version JSBridge protocol, the new version client can find the method for calling the historical version page from the compatible code base, and Call the historical version page through the found method for calling the historical version page. The specific implementation process is similar to the process of invoking the new version page by the historical version client, so it will not be repeated here.

The compatible code base is constructed by developers and maintained and updated, and the compatible code base stores the correspondence between the calling methods in the JSBridge protocols of each version. Therefore, when the detection result indicates that the version of the web page to be called is higher than the version of the current client, it is necessary to obtain from the compatible code base the method for calling the web page corresponding to the method agreed in the JSBridge protocol of the historical version The target calls the method to call the web page to be called.

For example, according to the JSBridge protocol of version 1.0, when the client of version 1.0 calls the corresponding web page of version 1.0, it uses method A. After an update, the web page is updated from version 1.0 to version 2.0. In this case The client may need to use the B method to call the 2.0 version of the web application according to the 2.0 version of the JSBridge protocol. It can be seen that the A method and the B method are to call methods of different versions of the same page. The corresponding relationship between method A and method B is stored in the compatible code base, and then when the client of version 1.0 needs to substitute the web page of version 2.0, the client can load the compatible code base to determine what method the client needs to use to call 2.0 version of the web page.

It should be noted that there are multiple calling methods for different versions of the same page stored in the compatible code base. For example, after the same web page has been updated several times, it forms version 1.0, version 2.0 and version 3.0. It is assumed that the web page of version 1.0 is called using method A, the web page of version 2.0 is called using method B, and the version 3.0 is called. If the web page uses the C method, the corresponding relationship of calling methods for these three versions of the page will be saved in the compatible code base.

In the embodiment of the present invention, after the current client successfully calls the web page according to the target calling method, the operation of uninstalling the compatible code base is performed, so that the storage space of the current client occupied by the compatible code base is released.

Here, the compatible code base is loaded by dynamic loading, that is, the compatible code base is loaded only when the compatible code base needs to be loaded, and unloaded when the compatible code base is not needed, which not only makes this loading method more efficient It is flexible and does not take up a lot of memory, and also enables the compatible code base to support hot updates, so that whenever the web page or client (native application) to be called is updated, developers can Update adjustments to compatible codebases.

FIG. 3 is a schematic diagram of the structure of a client version compatible device according to an embodiment of the present invention. As shown in FIG. 3 , the device includes: a receiving unit 301, a detecting unit 302, an intercepting unit 303, an obtaining unit 304, and a calling unit 305;

Wherein, the receiving unit 301 is configured to receive the loading request of the World Wide Web page sent by the current client;

The detection unit 302 is configured to, according to the loading request of the web page, detect whether the version of the web page to be called matches the version of the current client, and generate a detection result;

The intercepting unit 303 is configured to intercept, when the detection result indicates that the version of the web page to be invoked is higher than the version of the current client, intercept the use of the method agreed in the JSBridge protocol of the historical version compatible with the current client. web page to call;

The obtaining unit 304 is configured to obtain, from the compatible code base, the target calling method for calling the web page corresponding to the method agreed in the JSBridge protocol of the historical version;

The calling unit 305 is configured to call the web page according to the target calling method, so that the web page is displayed on the current client.

In this embodiment of the present invention, the device may be a smart terminal, for example, the smart terminal may be a desktop computer, a notebook computer, a smart phone, a tablet computer, a smart watch, or other devices. And, a Hybrid App is installed on the smart terminal.

Specifically, the Hybrid App refers to an APP between the WEB-APP and the Native-APP, and has both the "advantage of a good user interaction experience of the Native App" and the "advantage of the cross-platform development of the Web App".

Below, take the mobile APP as an example:

Native applications include: Kugou Music, Meitu Xiuxiu, such APPs can be called native applications;

Web applications include: ticket grabbing assistant and recharge easily opened through UC browser, these are web applications;

Hybrid applications include: Tmall, Ctrip, and 58.com. Most of them wrap web pages on the basis of native applications, such as 58.com's posts, Tmall's event pages, and Ctrip's order details pages. Embedding web pages to achieve search.

Take the PC APP as an example:

Native applications include: such as QQ, Thunder, etc.;

Web applications include: such as the once-popular web games;

Hybrid applications include: such as 360 mobile phone assistant.

In this embodiment of the present invention, the apparatus further includes: a sending unit 306;

Specifically, when the user wants to perform an opening operation on an object in the current client, the sending unit 306 in the terminal may be triggered to send a web page loading request to the client.

For example, when the user wants to adjust the "recharge center" application in the hybrid application "Alipay", by touching the icon corresponding to the "recharge center" with a finger, the sending unit 306 is triggered to send the client The loading request of the web page corresponding to the "recharge center" enables the client to receive the loading request of the web page. Specifically, the receiving unit 301 may receive the loading request of the web page.

In this embodiment of the present invention, after the receiving unit 301 receives the loading request of the web page, the web application part in the hybrid application does not directly call the code of the native application part through the calling unit 305, but According to the agreed rules between the web application part and the native application part, the JSBridge protocol can be used to inform the native application part of what needs to be done, and then the native application part can execute the corresponding code. Similarly, the native application part in the hybrid application does not directly call the code of the web application part through the calling unit 305, but can notify the web application through the JSBridge protocol according to the rules agreed between the web application part and the native application part. The part needs to do something, and then the web application part can execute the corresponding code.

Here, JSBridge is the communication bridge between Native code and JS code, because the communication between JS and Native must be realized through an H5 global object JSBridge, and the object name is "JSBridge", which is the global object window in the H5 page an attribute of . Therefore, in this embodiment of the present invention, when the native application executes the code for calling the web application part through the calling unit 305, the client needs to trigger the detection unit 302 to detect the version of the web page to be called and the version of the current client Whether it matches, get the test result. When the detection result indicates that the version of the web page to be invoked matches the version of the current client, the terminal triggers the invoking unit 305 to invoke the web page according to the page invocation method agreed in the JSBridge protocol. When the detection result indicates that the version of the web page to be called does not match the version of the current client, the intercepting unit 303 is triggered, and the intercepting unit 303 intercepts the calling unit 305 using a history compatible with the current client The method agreed in the version JSBridge protocol calls the web page;

It should be noted that when the developer updates the current client or the web page in the current client, after the update, the current client or web page will be marked with a specific identifier (such as a version number) at the same time, and then when the local client When the client calls a certain web page in the client through the calling unit 305, the current client can detect the version number of the web page to be called and the current client version number through the detection unit 302 to determine the version of the client Whether it matches the version of the web page to be called.

For example, if the developer develops a corresponding web page for the client of version 1.0 installed on the current terminal, and the version number of the web page is 2.1, when the user uses the client of version 1.0 to call the web page of version 2.1 later , the client of version 1.0 determines that the current version of the client of version 1.0 matches the version of the web page of version 2.1 to be called.

In this embodiment of the present invention, when the current client does not match the version of the web page to be called, at least one of the following situations is included:

Case 1: The current client detects through the detection unit 302 that the version of the web page to be called is higher than the version of the current client. That is to say, the version of the current client is lower than the version of the web page to be called, that is, the old client calls the new page;

At this time, the current client triggers the calling unit 305 to call the web page according to the method agreed in the JSBridge protocol of the historical version.

In this embodiment of the present invention, when the version of the web page to be called is higher than the version of the current client, at least one of the following scenarios is included, wherein:

Scenario 1: The new version page is obtained after updating the historical version page that can be called by the historical version client;

In this embodiment of the present invention, the apparatus further includes: a loading unit 307 and a searching unit 308;

In this case, the historical version client itself saves a method for calling the historical version page, so the terminal can trigger the loading unit 307 to load the compatible code base according to the method for calling the historical version page, and when the loading is successful Then, trigger the search unit 308 to search for a method for calling the new version page from the compatible code base, and after the search unit 308 finds the method for calling the new version page, trigger the calling unit 305 according to the The method for calling the new version page found by the searching unit 308 calls the new version page.

In this embodiment of the present invention, when the loading unit 307 loads the compatible code base, it will trigger the sending unit 306 to send a loading request for loading the compatible code base to the background server of the client; the loading request is When the background server responds successfully, the calling unit 305 is triggered to call the compatible code base, and the loading unit 307 loads the compatible code base, so that the obtaining unit 304 can obtain from the compatible code base The method is called to the target invoking the web page corresponding to the method agreed in the JSBridge protocol of the historical version.

For example, both the client before the update and the web page to be called are version 1.0, and the client and the web page use the version 1.0 JSBridge protocol to call each other. According to the 1.0 version of the JSBridge protocol, the The client can use method A to call the web page of version 1.0, and after the update, the web page is updated to version 2.0. When the user needs to call the web page of version 2.0 at this time, it needs to be based on the version 2.0 JSBridge protocol. In this case, when the client of version 1.0 triggers the calling unit 305 to call the web page of version 2.0 through method A, the client will trigger the loading unit 307 to load the underlying infrastructure library, the intercepting unit 303 will intercept the call initiated by the 1.0 version client through the A method, and then the terminal will trigger the search unit 308 In order to call the B method of the 2.0 version of the web page, the calling unit 305 can call the 2.0 version of the web page through the determined B method. The specific interaction flow between the client and the web page to be called is shown in FIG. 2 in the method embodiment.

In the embodiment of the present invention, the above invocation method avoids the problem of error reporting when the client invokes the web page due to incompatible versions between the client and the web page to be invoked.

Scenario 2: The new version page that the historical version client needs to call is the newly added page;

In this case, the apparatus further includes: an output unit 309;

Specifically, since the new version page is a newly added page, there is no historical version page corresponding to the new version page, so the historical version client itself does not save a method for calling the page, so the calling The unit 305 cannot find the method for invoking the new version page from the compatible code base, then the client will trigger the output unit 309 to output a message for prompting the user to update the current client version.

Here, the prompting method may be a voice prompt, or a pop-up "update window" on the display interface of the current client, or a prompt in the form of text characters.

Case 2: The version of the current client is higher than the version of the web page to be called, that is, the new client calls the old page;

In the case where the new client calls the old page, it is assumed that the new version client still has the page calling method according to the historical version of the JSBridge protocol. In this case, the new version of the client can directly use the historical version of the JSBridge protocol. The page call method of the page calls the historical version web page. When the new version client does not store the page calling method according to the JSBridge protocol of the historical version, in this case, the new version client can trigger the search unit 308 to search for the calling history from the compatible code base version page, and trigger the calling unit 305 to call the historical version page through the found method for calling the historical version page. The specific implementation process is similar to the process of the historical version client calling the new version page, so here It is not repeated here.

In the embodiment of the present invention, the compatible code base is constructed by developers and maintained and updated, and the compatible code base stores the correspondence between the calling methods in the JSBridge protocol of each version. Therefore, when the detection result obtained by the detection unit 302 indicates that the version of the web page to be called is higher than the version of the current client, the acquisition unit 304 needs to be triggered to acquire the JSBridge protocol with the historical version from the compatible code base The method agreed in the corresponding to the target invocation method of invoking the web page, so that the invoking unit 305 invokes the web page to be invoked.

For example, according to the JSBridge protocol of version 1.0, when the client of version 1.0 calls the corresponding web page of version 1.0, it uses method A. After an update, the web page is updated from version 1.0 to version 2.0. In this case The client may need to use the B method to call the 2.0 version of the web application according to the 2.0 version of the JSBridge protocol. It can be seen that the A method and the B method are to call methods of different versions of the same page. The corresponding relationship between method A and method B is stored in the compatible code base, and then when the client of version 1.0 needs to substitute the web page of version 2.0, the client can load the compatible code base to determine what method the client needs to use to call 2.0 version of the web page.

It should be noted that there are multiple calling methods for different versions of the same page stored in the compatible code base. For example, after the same web page has been updated several times, it forms version 1.0, version 2.0 and version 3.0. It is assumed that the web page of version 1.0 is called using method A, the web page of version 2.0 is called using method B, and the version 3.0 is called. If the web page uses the C method, the corresponding relationship of calling methods for these three versions of the page will be saved in the compatible code base.

In this embodiment of the present invention, the apparatus further includes: an unloading unit 310;

Specifically, after the calling unit 305 successfully calls the web page according to the target calling method, triggers the uninstalling unit 310 to perform an uninstallation operation on the compatible code base, so that the current client can release the compatible code base Occupies the storage space of the current client.

Here, the compatible code base is loaded by dynamic loading, that is, the compatible code base is loaded only when the compatible code base needs to be loaded, and unloaded when the compatible code base is not needed, which not only makes this loading method more efficient It is flexible and does not take up a lot of memory, and also enables the compatible code base to support hot updates, so that whenever the web page or client (native application) to be called is updated, developers can Update adjustments to the compatible codebase.

In the embodiment of the present invention, by loading a compatible code base in the historical version client, when the historical version client loads a new version of the page and calls the new version of the JSBridge protocol, the historical version client will call the underlying basic library and intercept according to the new version of the JSBridge protocol. The call is made according to the JSBridge protocol compatible with the historical version of the client, and then the call is made according to the compatible method of the historical version of the client. Through this scheme, developers do not need to target various The historical version client respectively integrates the "historical version JSBridge protocol" compatible with the historical version client, and does not require users to update the historical version client.

The embodiment of the present invention also provides another client version compatible device, the device includes: a memory and a processor;

Wherein, the memory is used to store a computer program that can run on the processor;

The processor, when running the computer program, executes: receiving a request for loading a World Wide Web page sent by the current client;

According to the loading request of the web page, detect whether the version of the web page to be called matches the version of the current client, and generate a detection result;

When the detection result indicates that the version of the web page to be called is higher than the version of the current client, intercepting and using the method agreed in the JSBridge protocol of the historical version compatible with the current client to call the web page;

Obtain from the compatible code base the target invocation method for invoking the web page corresponding to the method agreed in the historical version JSBridge protocol;

The web page is invoked according to the target invocation method, so that the web page is displayed on the current client.

The processor, when running the computer program, further executes: when the detection result indicates that the version of the web page to be called is lower than the version of the current client, according to the historical version agreed in the JSBridge protocol. method calls the web page.

The processor, when running the computer program, further executes: when the detection result indicates that the version of the web page to be called is the version of the newly added page, the output is used for prompting the user to perform the operation on the current client. Version update news.

The processor, when running the computer program, further executes: sending a loading request for loading the compatible code base;

When the loading request is successfully responded, the compatible code base is loaded, so that the target calling method for calling the web page corresponding to the method agreed in the JSBridge protocol of the historical version is obtained from the compatible code base.

The processor, when running the computer program, further executes: after successfully calling the web page according to the target calling method, unloading the compatible code base, so that the compatible code base is released to occupy the storage of the current client space.

4 is a schematic diagram of the structure of the client version compatible device, the client version compatible device 400 can be a mobile phone, a computer, a digital broadcasting terminal, an information sending and receiving device, a game console, a tablet device, a personal digital assistant, and an information push server , content server, etc. The client version compatible apparatus 400 shown in FIG. 4 includes: at least one processor 401 , memory 402 , at least one network interface 404 and user interface 403 . The various components in client version compatible device 400 are coupled together by bus system 405 . It can be understood that the bus system 405 is used to implement the connection communication between these components. In addition to the data bus, the bus system 405 also includes a power bus, a control bus, and a status signal bus. However, for clarity of illustration, the various buses are labeled as bus system 405 in FIG. 4 .

The user interface 403 may include a display, a keyboard, a mouse, a trackball, a click wheel, keys, buttons, a touch pad or a touch screen, and the like.

It will be appreciated that the memory 402 may be either volatile memory or non-volatile memory, and may include both volatile and non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM, Read Only Memory), a programmable read-only memory (PROM, Programmable Read-Only Memory), an erasable programmable read-only memory (EPROM, Erasable Programmable Read-only memory) Only Memory), Electrically Erasable Programmable Read-Only Memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), Magnetic Random Access Memory (FRAM, ferromagnetic random access memory), Flash Memory (Flash Memory), Magnetic Surface Memory , CD-ROM, or Compact Disc Read-Only Memory (CD-ROM, Compact Disc Read-Only Memory); the magnetic surface memory can be a magnetic disk memory or a tape memory. The volatile memory may be Random Access Memory (RAM), which is used as an external cache memory. By way of example and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory Memory (DRAM, Dynamic Random Access Memory), Synchronous Dynamic Random Access Memory (SDRAM, SynchronousDynamic Random Access Memory), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM, Double Data Rate Synchronous Dynamic Random Access Memory), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM, Enhanced Synchronous Dynamic Random Access Memory), Synchronous Link Dynamic Random Access Memory (SLDRAM, SyncLink Dynamic Random Access Memory), Direct Memory Bus Random Access Memory (DRRAM, Direct Rambus Random Access Memory) . The memory 402 described in the embodiments of the present invention is intended to include, but not be limited to, these and any other suitable types of memory.

The memory 402 in the embodiment of the present invention is used for storing various types of data to support the operation of the device 400 compatible with the client version. Examples of such data include: any computer program for operating on client version compatible device 400, such as operating system 4021 and application programs 4022; music data; animation data; book information; videos, and the like. The operating system 4021 includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks. The application program 4022 may include various application programs, such as a media player (Media Player), a browser (Browser), etc., for implementing various application services. A program for implementing the method of the embodiment of the present invention may be included in the application program 4022 .

The methods disclosed in the above embodiments of the present invention may be applied to the processor 401 or implemented by the processor 401 . The processor 401 may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above-mentioned method can be completed by an integrated logic circuit of hardware in the processor 401 or an instruction in the form of software. The above-mentioned processor 401 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. The processor 401 may implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in combination with the embodiments of the present invention can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, and the storage medium is located in the memory 402, and the processor 401 reads the information in the memory 402, and completes the steps of the foregoing method in combination with its hardware.

In an exemplary embodiment, the client version compatible device 400 may be implemented by one or more Application Specific Integrated Circuit (ASIC, Application Specific Integrated Circuit), DSP, Programmable Logic Device (PLD, Programmable Logic Device), complex programmable Logic Device (CPLD, Complex Programmable LogicDevice), Field Programmable Gate Array (FPGA, Field-Programmable Gate Array), General Purpose Processor, Controller, Microcontroller (MCU, Micro Controller Unit), Microprocessor (Microprocessor), or other electronic components to implement the aforementioned method.

In an exemplary embodiment, the embodiment of the present invention further provides a computer-readable storage medium, such as a memory 402 including a computer program, and the above-mentioned computer program can be executed by the processor 401 of the device 400 that is compatible with the client version, so as to complete the foregoing the steps of the method. The computer-readable storage medium can be memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disk, or CD-ROM; it can also be various devices including one or any combination of the above-mentioned memories, such as Mobile phones, computers, tablet devices, personal digital assistants, etc.

A computer-readable storage medium on which a computer program is stored, and when the computer program is run by a processor, executes: receiving a request for loading a World Wide Web page sent by a current client;

According to the loading request of the web page, detect whether the version of the web page to be called matches the version of the current client, and generate a detection result;

When the detection result indicates that the version of the web page to be called is higher than the version of the current client, intercepting and using the method agreed in the JSBridge protocol of the historical version compatible with the current client to call the web page;

Obtain from the compatible code base the target invocation method for invoking the web page corresponding to the method agreed in the historical version JSBridge protocol;

The web page is invoked according to the target invocation method, so that the web page is displayed on the current client.

When the computer program is run by the processor, it further executes: when the detection result indicates that the version of the web page to be called is lower than the version of the current client, calling the web page according to the method agreed in the JSBridge protocol of the historical version page.

When the computer program is run by the processor, the computer program further executes: when the detection result indicates that the version of the web page to be called is the version of the newly added page, outputting a message for prompting the user to update the current client version.

When the computer program is run by the processor, it also executes: sending a loading request for loading the compatible code base;

When the loading request is successfully responded, the compatible code base is loaded, so that the target calling method for calling the web page corresponding to the method agreed in the JSBridge protocol of the historical version is obtained from the compatible code base.

When the computer program is run by the processor, it further executes: after successfully calling the web page according to the target calling method, uninstalling the compatible code base, so that the compatible code base is released to occupy the storage space of the current client.

The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention. should be included within the protection scope of the present invention.

Claims (12)

1. A method for client version compatibility, wherein the method comprises: Receive the loading request of the World Wide Web page sent by the current client; According to the loading request of the web page, detect whether the version of the web page to be called matches the version of the current client, and generate a detection result; When the detection result indicates that the version of the web page to be called is higher than the version of the current client, intercepting and using the method agreed in the JSBridge protocol of the historical version compatible with the current client to call the web page; Obtain from the compatible code base the target invocation method for invoking the web page corresponding to the method agreed in the historical version JSBridge protocol; The web page is invoked according to the target invocation method, so that the web page is displayed on the current client. 2. The method according to claim 1, wherein the method further comprises: When the detection result indicates that the version of the web page to be invoked is lower than the version of the current client, the web page is invoked according to the method agreed in the JSBridge protocol of the historical version. 3. The method according to claim 1, wherein the method further comprises: When the detection result indicates that the version of the web page to be called is the version of the newly added page, a message for prompting the user to update the version of the current client is output. 4. The method according to claim 1, wherein when the detection result indicates that the version of the web page to be called is higher than the version of the current client, the method further comprises: sending a load request to load the compatible code base; When the loading request is successfully responded, the compatible code base is loaded, so that the target calling method for calling the web page corresponding to the method agreed in the JSBridge protocol of the historical version is obtained from the compatible code base. 5. The method according to claim 1, wherein the method further comprises: After the web page is successfully called according to the target calling method, the compatible code base is uninstalled, so that the storage space of the current client occupied by the compatible code base is released. 6. A client version compatible device, characterized in that the device comprises: a receiving unit, a detecting unit, an intercepting unit, an acquiring unit, and a calling unit; Wherein, the receiving unit is used to receive the loading request of the World Wide Web page sent by the current client; The detection unit is configured to, according to the loading request of the web page, detect whether the version of the web page to be called matches the version of the current client, and generate a detection result; The intercepting unit is configured to intercept, when the detection result indicates that the version of the web page to be called is higher than the version of the current client, intercept the web page using the method agreed in the JSBridge protocol of the historical version compatible with the current client. page to call; The obtaining unit is used to obtain the target calling method of calling the web page corresponding to the method agreed in the historical version JSBridge protocol from the compatible code base; The calling unit is configured to call the web page according to the target calling method, so that the web page is displayed on the current client. 7. The apparatus according to claim 6, wherein the calling unit is further configured to, when the detection result indicates that the version of the web page to be called is lower than the version of the current client, according to the history The method agreed in the version JSBridge protocol invokes the web page. 8. The device according to claim 6, wherein the device further comprises: an output unit, The output unit is configured to output a message for prompting the user to update the version of the current client when the detection result indicates that the version of the web page to be called is the version of the newly added page. 9. The apparatus according to claim 6, wherein the apparatus further comprises: a sending unit and a loading unit; the sending unit, configured to send a loading request for loading the compatible code base when the detection result indicates that the version of the web page to be called is higher than the version of the current client; The loading unit is used to load the compatible code base when the load request is successfully responded, so that the web page corresponding to the method agreed in the historical version JSBridge protocol is obtained from the compatible code base The target calls the method. 10. The device according to claim 6, wherein the device further comprises: an unloading unit; The unloading unit is configured to unload the compatible code base after successfully calling the web page according to the target calling method, so that the storage space of the current client occupied by the compatible code base is released. 11. A client version compatible device, wherein the device comprises: a memory and a processor; Wherein, the memory is used to store a computer program that can run on the processor; The processor is configured to execute the steps of the method according to any one of claims 1 to 5 when running the computer program. 12. A computer-readable storage medium on which a computer program is stored, characterized in that, when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 are implemented.

Images