WO2016192556A1

WO2016192556A1 - Interface invoking method, device and terminal

Info

Publication number: WO2016192556A1
Application number: PCT/CN2016/083359
Authority: WO
Inventors: 刘争辉
Original assignee: 北京金山安全软件有限公司
Priority date: 2015-05-29
Filing date: 2016-05-25
Publication date: 2016-12-08
Also published as: CN104866383B; CN104866383A

Abstract

Disclosed in embodiments of the present invention are an interface invoking method and terminal. The method comprises: receiving an interface invoking request, the interface invoking request carrying an interface identifier and an interface parameter corresponding to a target interface required to be invoked by a client script; determining, according to the interface identifier, an invoking mode of the target interface; determining, according to the invoking mode and the interface parameter, a first parameter in input parameters of a target interface function corresponding to the target interface; invoking the target interface function by utilizing a request identifier of the interface invoking request and the first parameter as the input parameters of the target interface function; acquiring output parameters returned after invoking the target interface function, the output parameters comprising the request identifier and a second parameter; and returning, based on the second parameter, an invoking result of the interface invoking request corresponding to the request identifier to the client script. The embodiments of the present invention improve a development efficiency of an expansion interface.

Description

Interface calling method, device and terminal

Cross-reference to related applications

The present application is based on a Chinese patent application filed on Jan. 29, 2015, the entire disclosure of which is hereby incorporated by reference.

Technical field

The present invention relates to the field of computer technologies, and in particular, to an interface calling method, apparatus, and terminal.

Background technique

With the development of Internet technology, the browser has become one of the necessary application software on the mobile terminal. When browsing the webpage through the browser on the mobile terminal, the browser kernel interprets and renders the webpage syntax. Generally, the browser kernel provides some standard interfaces for the client script to use or call. Therefore, by loading the client script in the webpage and interpreting and executing the client script by the browser, the dynamic display effect of the webpage can be realized, and the interaction of the webpage is enhanced. Sex. For example: implement special display effects of page elements, respond to user actions, validate form data, and more.

However, the standard interface provided by the browser kernel itself is limited. Therefore, in order to meet the development needs of Web pages, developers need to develop more extension interfaces as needed for client-side scripting of Web pages. At present, because the standards for developing extended interfaces are not uniform, there is no unified interface calling method for handling client-side scripts to call any extended interface. Therefore, when developing an extended interface, developers need not only the functions provided by the extended interface. Design an interface function, and also need to design a processing method for the interface to call the interface for the extended interface. For example, the existing interface development method is shown in Figure 1a. When developing interface A and interface B, in addition to developing the interface function of interface A and the interface function of interface B, it is necessary to develop a script call interface A for interface A. The calling method and the calling method when developing a set of scripts for interface B to invoke interface B result in low development efficiency.

Summary of the invention

The embodiment of the invention provides an interface calling method, device and terminal, which can improve the development efficiency of the extended interface.

In a first aspect, an embodiment of the present invention provides an interface calling method, including:

Receiving an interface call request, where the interface call request carries an interface identifier and an interface parameter corresponding to the target interface that the client script needs to call, and the target interface is one of the extended interfaces provided by the browser;

Determining, according to the interface identifier, a calling manner of the target interface;

Determining, according to the calling mode and the interface parameter, an input parameter of a target interface function corresponding to the interface identifier The first parameter in ;

Calling the request identifier of the interface call request and the first parameter as input parameters of the target interface function, and calling the target interface function;

Obtaining an output parameter returned after the target interface function is invoked, where the output parameter includes the request identifier and the second parameter;

And returning, according to the second parameter, a call result of the interface call request corresponding to the request identifier to the client script.

In a first possible implementation manner of the first aspect, the data type of the output parameter is a preset first data type;

After the first parameter in the input parameter of the target interface function corresponding to the target interface is determined according to the calling mode and the interface parameter, the method further includes:

Formatting the first parameter, and the data type of the converted first parameter is a preset second data type;

After the obtaining the output parameter that is returned after the target interface function is invoked, after the output parameter includes the request identifier and the second parameter, the method further includes:

Converting the second parameter into a format, and the data type of the converted second parameter is a preset third data type.

With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the determining, according to the calling manner and the interface parameter, The first parameter in the input parameters of the target interface function includes:

If the calling mode is a synchronous call, determining the interface parameter as the first parameter in the input parameter of the target interface function;

If the calling mode is an asynchronous call, the other parameters of the interface parameter except the preset parameter are determined as the first parameter in the input parameter of the target interface function, and the preset parameter is used to identify the callback function.

With reference to the first aspect, or the first possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, the request, according to the second parameter, The result of the call returned to the client script includes:

If the calling mode is a synchronous call, the second parameter is returned to the client script as a result of the call of the interface call request corresponding to the request identifier;

If the calling mode is an asynchronous call, determining a target callback function corresponding to the request identifier, and using the second parameter as an input parameter of the target callback function, running the target callback function to obtain an output result, and then The output result is returned to the client script as a result of the call of the interface call request.

In conjunction with the third possible implementation of the first aspect, in a fourth possible implementation of the first aspect, After determining the calling mode of the target interface according to the interface identifier, the method further includes:

If the calling mode is an asynchronous call, the callback information is saved in the callback database, where the callback information includes the request identifier and a callback function identified by the preset parameter;

Determining the target callback function corresponding to the request identifier, including:

If the calling mode is an asynchronous call, query the callback information corresponding to the request identifier from the callback database according to the request identifier;

The callback function specified by the callback information is determined as a target callback function.

In conjunction with the fourth possible implementation of the first aspect, in a fifth possible implementation manner of the first aspect, the second parameter is returned to the call result of the interface call request corresponding to the request identifier to After the client script, the method further includes:

Deleting the callback information corresponding to the request identifier in the callback database.

With reference to the first aspect, or the first possible implementation manner of the first aspect, in a sixth possible implementation manner of the first aspect, the determining, by the interface identifier, the calling manner of the target interface includes:

Querying, according to the interface identifier, the interface information corresponding to the interface identifier from a preset interface database, where the interface information includes an interface identifier and a calling mode;

The calling mode corresponding to the interface identifier in the interface database is determined as the calling mode of the target interface.

In a second aspect, an embodiment of the present invention provides an interface calling apparatus, including:

a receiving module, configured to receive an interface call request, where the interface call request carries an interface identifier and an interface parameter corresponding to the target interface that the client script needs to invoke, and the target interface is one of the extended interfaces provided by the browser;

a mode determining module, configured to determine, according to the interface identifier, a calling mode of the target interface;

a parameter determining module, configured to determine, according to the calling manner and the interface parameter, a first parameter in an input parameter of a target interface function corresponding to the interface identifier;

a calling module, configured to invoke the request identifier of the interface call request and the first parameter as an input parameter of the target interface function, and invoke the target interface function;

An obtaining module, configured to obtain an output parameter returned after the target interface function is invoked, where the output parameter includes the request identifier and the second parameter;

And a returning module, configured to return, according to the second parameter, a call result of the interface call request corresponding to the request identifier to the client script.

In a first possible implementation manner of the second aspect, the data type of the output parameter is a preset first data type, and the device further includes:

a first conversion module, configured to perform format conversion on the first parameter, and the data type of the converted first parameter is a pre- The second data type set;

The second conversion module is configured to perform format conversion on the second parameter, and the data type of the converted second parameter is a preset third data type.

With reference to the second aspect or the first possible implementation manner of the second aspect, in the second possible implementation manner of the second aspect, the parameter determining module is specifically configured to:

In conjunction with the second aspect, or the first possible implementation of the second aspect, in a third possible implementation of the second aspect, the returning module includes:

Synchronizing the returning unit, if the calling mode is a synchronous call, returning the second parameter to the client script as a result of calling the interface call request corresponding to the request identifier;

An asynchronous return unit, if the calling mode is an asynchronous call, determining a target callback function corresponding to the request identifier, and using the second parameter as an input parameter of the target callback function, running the target callback function to obtain an output result And returning the output result to the client script as a result of the call of the interface call request.

In conjunction with the third possible implementation of the second aspect, in a fourth possible implementation of the second aspect, the device further includes:

a saving module, configured to save the callback information to the callback database if the calling mode is an asynchronous call, where the callback information includes the request identifier and a callback function identified by the preset parameter;

The synchronous return unit is specifically configured to:

In conjunction with the fourth possible implementation of the second aspect, in a fifth possible implementation of the second aspect, the device further includes:

And a deleting module, configured to delete the callback information corresponding to the request identifier in the callback database.

With reference to the second aspect, or the fifth possible implementation manner of the second aspect, in the sixth possible implementation manner of the second aspect, the mode determining module is specifically configured to:

In a third aspect, an embodiment of the present invention provides an interface calling apparatus, including at least one processor and a memory storing instructions executable by at least one processor. At least one processor is configured to: receive an interface call request, where the interface call request carries an interface identifier and an interface parameter corresponding to the target interface that the client script needs to invoke, and the target interface is one of the extended interfaces provided by the browser; Determining, by the interface identifier, a calling mode of the target interface; determining, according to the calling mode and the interface parameter, a first parameter in an input parameter of a target interface function corresponding to the interface identifier; Calling the target interface function as the input parameter of the target interface function, and acquiring an output parameter returned after calling the target interface function, where the output parameter includes the request identifier and the a second parameter, based on the second parameter, returning a call result of the interface call request corresponding to the request identifier to the client script.

In a fourth aspect, an embodiment of the present invention provides an interface calling device, including: an interface registrar, configured to record registration information of an interface, where registration information of the interface includes an interface identifier and a calling mode of the interface, and an interface database for storing Interface information of each interface; a request request database for storing the call request identifier and calling mode; a parameter converter for receiving an interface call request of the client script, the interface call request carrying a target that the client script needs to call An interface identifier and an interface parameter corresponding to the interface, where the target interface is one of the extended interfaces provided by the browser; determining, according to the interface identifier, a calling mode of the target interface; according to the calling mode and the interface parameter, Determining, by the interface proxy, the first parameter in the input parameter of the target interface function corresponding to the interface identifier; the interface proxy is configured to obtain the call information required by the interface call request, where the call information includes a request identifier, an interface identifier, and a first parameter And calling mode; and reconstructing the interface according to the obtained call information Receiving, by the interface forwarder, the reconstructed interface call request sent by the interface proxy; adding a request identifier and a calling manner in the interface call request to the call request database; and querying according to the interface identifier Obtaining, by the interface registrar, a target interface function corresponding to the interface identifier, acquiring a location of a target interface function corresponding to the target interface, and using the request identifier and the first parameter as input parameters of the queried target interface function, Calling the target interface function; the interface notifier is configured to obtain an output parameter after the target interface function is completed, the output parameter includes the request identifier and the second parameter, and the second parameter is corresponding to the request identifier The result of the call of the interface call request; searching for the corresponding call request and the calling mode in the call request database according to the request identifier; and sending the output parameter to the interface proxy if the calling mode is a synchronous call

According to a fifth aspect, an embodiment of the present invention provides a terminal, including the interface calling device according to the second aspect, the third aspect, or the fourth aspect.

In a sixth aspect, an embodiment of the present invention provides a computer readable storage medium having instructions stored therein, and when a processor of a terminal executes the instruction, the terminal executes an interface calling method as described above.

In a seventh aspect, an embodiment of the present invention provides a computer program that, when run on a processor, performs the above The interface call method.

In the embodiment of the present invention, the interface call request is received, and the interface call request carries an interface identifier and an interface parameter corresponding to the target interface that the client script needs to invoke, and the target interface is one of the extended interfaces provided by the browser; Determining, by the interface identifier, a calling mode of the target interface; determining, according to the calling mode and the interface parameter, a first parameter in an input parameter of a target interface function corresponding to the interface identifier; Calling the target interface function as the input parameter of the target interface function, and acquiring an output parameter returned after calling the target interface function, where the output parameter includes the request identifier and the a second parameter, based on the second parameter, returning a call result of the interface call request corresponding to the request identifier to the client script. By adopting the embodiment of the present invention, through the design of the normalized interface function and the interface call, the browser can adopt a unified interface calling method to implement the call of the client script to any extended interface. Therefore, when developers develop an extension interface, it is only necessary to develop an interface function corresponding to the extension interface, which can improve the development efficiency of the extension interface.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are some embodiments of the present invention, Those skilled in the art can also obtain other drawings based on these drawings without paying any creative work.

Figure 1a is a schematic diagram of an interface call provided by the prior method;

1 is a schematic flowchart of an interface calling method according to an embodiment of the present invention;

Figure 1b is a schematic diagram of an interface call provided in Figure 1;

2 is another schematic flowchart of an interface calling method according to an embodiment of the present invention;

3 is a schematic structural diagram of an interface calling apparatus according to an embodiment of the present invention;

4 is another schematic structural diagram of an interface calling apparatus according to an embodiment of the present invention;

4a is a schematic structural view of one of the return modules provided in FIG. 4;

FIG. 5 is still another schematic structural diagram of an interface calling apparatus according to an embodiment of the present disclosure;

FIG. 6 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure;

FIG. 7 is still another schematic structural diagram of an interface calling apparatus according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts, All fall within the scope of protection of the present invention.

The embodiment of the present invention provides an interface calling method, device, and terminal. The interface calling method, device, and terminal provided by the embodiment of the present invention are respectively described in detail in conjunction with FIG.

Referring to FIG. 1, FIG. 1 is a schematic flowchart of a method for invoking an interface according to an embodiment of the present invention. In the embodiment of the present invention, the method may include the following steps.

S101: Receive an interface call request, where the interface call request carries an interface identifier and an interface parameter corresponding to the target interface that the client script needs to call, and the target interface is one of the extended interfaces provided by the browser.

The method described in the embodiment of the present invention may be used in a browser on a terminal or a browser-like product. The terminal may be a terminal such as a computer, an IPAD, a mobile phone, or other smart device. Specifically, The embodiment of the invention does not impose any limitation.

Generally, in order to enrich the dynamic display effect of the webpage and enhance the interaction between the webpage and the user, the browser provides a large number of interfaces to the webpage for the client script to be loaded in the webpage, and the browser interprets and executes the client script. For example, when the browser receives the interface call request of the client script, the browser runs the interface function corresponding to the target interface specified by the information according to the information carried by the interface call request, thereby implementing the corresponding function. Therefore, in the process of loading the webpage, if the client script in the webpage needs to invoke the extension interface provided by the browser, the browser receives the interface call request.

S102: Determine, according to the interface identifier, a calling manner of the target interface.

The calling mode of the interface includes a synchronous call and an asynchronous call. The synchronous call is a blocking call, and the caller waits for the callee to return after executing, and belongs to a one-way call; the asynchronous call is a two-way call, similar to The processing mechanism of the message or event, the caller only has an operation request, and returns immediately after the callee finishes executing. After the execution, the callee actively calls the callback function (callback) provided by the caller to return the execution result to the call. Therefore, asynchronous calls can improve the efficiency of the browser executing web pages. Usually, after the developer develops the interface function of the extended interface, the calling mode of the interface is preset according to the function implemented by the extended interface. For example, if the client script invokes the interface A, the subsequent operations can be performed without the return result of the interface A. To improve the running efficiency of the web page, the calling mode of the interface A can be set to be asynchronously invoked, thereby the interface parameters of the interface A. There is a parameter indicating the callback function, which is independent of the specific function that the interface needs to implement, and is used to return the running result of the interface. For example, if the client script invokes interface B and the return result of interface B is the premise of subsequent operations, the call mode of interface B can be set to synchronous call.

As an example, the interface information of the extended interface may be recorded in the preset interface database, where the interface information includes an interface identifier and a calling mode, and the interface identifier may be an interface name of the interface function, or may be an interface name. The other identifiers of the one-to-one correspondence are not limited in the embodiment of the present invention; the calling modes include synchronous calling and asynchronous calling. For the convenience of description, suppose the interface identifier is the interface name, and there are three extension interfaces provided, then the interface database is saved. The storage format can be as shown in Table 1. Table 1 is a schematic diagram of storage of an interface database according to an embodiment of the present invention.

Table 1

As shown in Table 1, in the extended interface provided by the browser, the call mode corresponding to the interface whose interface identifier is "recordHistory" and "downloadUrl" is called asynchronously, and the interface whose interface identifier is "playAudio" corresponds to the calling mode. Called for synchronization. Therefore, in the embodiment of the present invention, the calling mode of the target interface corresponding to the interface identifier may be queried from the interface database according to the interface identifier carried in the interface call request.

As another example, the interface parameter carried in the interface call request may include a parameter that identifies a calling mode of the target interface. For example, it can be assumed that the first parameter in the interface parameter is used to indicate the calling mode of the target interface. The "1" is used to indicate the synchronous call, and the "0" is used to indicate the asynchronous call. Of course, the parameter indicating the calling mode of the target interface can also be The parameter at the other position in the interface parameter indicates that the specific value of the calling mode may be other characters, which is not limited in the embodiment of the present invention. However, based on the assumption, the calling mode of the target interface may be determined according to the specific value of the first parameter in the interface parameter. If the parameter is set to "1", the calling mode of the target interface corresponding to the interface identifier may be determined to be synchronously invoked; If it is "0", it can be determined that the calling mode corresponding to the interface identifier is asynchronously called. It should be noted that, in the embodiment of the present invention, the specific form of the parameter of the calling mode of the calibration target interface is not limited, and the calibration rule may be agreed in advance. In the embodiment of the present invention, the calling mode of the target interface corresponding to the interface identifier may be determined according to the interface parameter carried in the interface call request. To facilitate the description of the subsequent steps, the first embodiment of the present invention is taken as an example.

S103: Determine, according to the calling manner and the interface parameter, a first parameter in an input parameter of a target interface function corresponding to the interface identifier.

Since the browser has a difference in handling the asynchronous call and the synchronous call of the interface call request, the asynchronous call requires the caller to provide a parameter identifying the callback function, and the callee returns the execution result of the target interface function through the callback function after the execution is completed. The synchronous call is the result of the caller returning directly to the target interface function after execution. Therefore, if the calling mode is asynchronous, the interface parameter carried by the interface calling request has a preset parameter that identifies a callback function, and the preset parameter is provided by the caller, and the called party is responsible for calling the preset parameter. The callback function for the identity.

In the embodiment of the present invention, the manner in which the client script invokes the interface is normalized, for example, the script indicating the synchronous call and the asynchronous call may be as shown in the code 1.

Code 1

/ / Synchronous call, the result of the operation is obtained by the return value

Function syncInterface(arg1, arg2,...);

/ / Asynchronous call, the result of the operation is obtained through callback function callback

Function asyncInterface(arg1, arg2, ..., callback);

/ / callback function specification

Function asyncCallback(Object);

As can be seen from the code 1, the embodiment of the present invention normalizes the specification of the script call interface, wherein the number of interface parameters (arg1, arg2, etc.) and the data type are set according to actual needs. In the asynchronous call, the last parameter in the interface parameter can be used to represent the parameter of the callback function. Of course, it can also be the parameter at the other position in the interface parameter. Specifically, the embodiment of the present invention does not limit, and the agreement is reached in advance. Just fine. The callback function in the asynchronous call is used to notify the client script of the result of the call. The specification of the callback function is also listed in code 1. It accepts an input parameter, and the type of the input parameter can be a common data type supported by the script. For example: Object object.

In the embodiment of the present invention, if the calling mode is a synchronous call, the first parameter in the input parameter of the target interface function corresponding to the target interface may be directly determined according to the interface parameter carried in the interface call request. If the calling mode is asynchronous, the first parameter in the input parameter of the target interface function corresponding to the target interface is determined according to the interface parameter carried in the interface call request, and the other parameters of the interface parameter except the preset parameter are Set parameters to identify the callback function, and each preset parameter corresponds to a callback function.

S104: Call the request identifier of the interface call request and the first parameter as an input parameter of the target interface function, and invoke the target interface function.

In a specific implementation, before the target interface function is invoked by using the request identifier of the interface call request and the first parameter as an input parameter of the target interface function, the request identifier of the interface call request may be determined. Further, considering that the browser processes the webpage, there may be a case of processing multiple interface call requests at the same time. Therefore, the request identifier is used to calibrate each interface call request of the client script call interface, and the request identifier corresponds to The interface invokes all the information associated with the request, the information including the interface identifier of the interface call request, the interface parameter, the call result, and the like, thereby tracking each interface call request and the call result by the request identifier. In the embodiment of the present invention, after receiving the interface call request, determining the request identifier of the interface call request, where the request identifier may be automatically allocated when the browser kernel receives the interface call request. It can be seen that a request identifier uniquely aligns an interface call request, and the request identifier is associated with an interface identifier and an interface parameter carried in the interface call request.

In the embodiment of the present invention, the design mode of the interface function is normalized, that is, each interface function receives one request identifier as one of the parameters of the input parameter, and the request identifier is also used as one of the parameters of the output parameter. For example, the request identifier is one of the input parameters of the interface function, that is, the input parameter includes the request identifier and the first parameter; the request identifier is one of the parameters of the output parameter of the interface function, that is, the output parameter includes the request identifier and the The second parameter, the request identifier and the second parameter association. Therefore, after the execution of the interface function is completed, the output parameter of the interface function is obtained, and the output parameter includes a request identifier and a second parameter, and the request result identifies the call result of the interface call request by the second parameter associated with the request identifier.

In a specific implementation, the request identifier and the first parameter are used as input parameters of the target interface function corresponding to the target interface, and the target interface function is invoked, that is, the target interface function is run.

S105: Acquire an output parameter returned after calling the target interface function, where the output parameter includes the request identifier and the second parameter.

In the embodiment of the present invention, the output parameter of the interface function includes a request identifier and a second parameter, where the second parameter is a parameter used by the interface function to implement the interface function and is returned to the client script, and the request identifier is used to identify the second parameter. The parameter is the result of the call to the request of the interface of the client script.

In a specific implementation, after the target interface function is completed, an output parameter returned after the target interface function is invoked is obtained, where the output parameter includes the request identifier and the second parameter.

S106: Return, according to the second parameter, a call result of the interface call request corresponding to the request identifier to the client script.

As an example, if the calling mode is a synchronous call, since the calling party needs to wait for the called party to return the calling result and then perform the subsequent operation, the second parameter is directly returned to the calling as the calling result of the interface calling request corresponding to the request identifier. a party, wherein the request identifier is associated with the second parameter.

As another example, if the calling mode is an asynchronous call, since the caller can continue to perform subsequent operations without waiting for the callee to return the call result, the call result is returned to the caller through the callback function. Therefore, the called party uses the second parameter as an input parameter of the callback function, and returns the call result of the interface call request corresponding to the request identifier to the caller by calling the callback function, wherein the request identifier is associated with the second parameter, and the callback is The function is a preset parameter that is calibrated in the interface parameter carried by the interface request request corresponding to the request identifier. Understandably, the caller is a client-side script and the callee is a browser. Thus, the result of the call of the interface call request is returned to the client script, and the call of the interface is completed.

For convenience of description, the method of the present invention can be understood as an interface intermediate layer, as shown in FIG. 1b, and FIG. 1b is a schematic diagram of an interface call provided in FIG. In the process of executing the webpage, if the client script in the webpage needs to invoke the extension interface provided by the browser, the interface middle layer receives the interface call request, and the interface call request carries the target interface that the client script needs to call. Interface identifier and interface parameters, wherein the target interface is an extension provided by the browser Any expansion interface in the port; the target interface function corresponding to the target interface is invoked by the above method, and the running result of the target interface function is returned to the client script as a result of the call of the interface call request. Therefore, through the intermediate layer of the interface to uniformly process the calling process of the interface, when developing the extended interface, the developer only needs to develop a corresponding interface function for the extended interface, and it is not necessary to design a set of the interface for each extended interface. Method to reduce workload and improve development efficiency.

In the interface calling method described in the embodiment of the present invention, an interface call request is received, where the interface call request carries an interface identifier and an interface parameter corresponding to a target interface that the client script needs to invoke, and the target interface is provided by the browser. Determining, according to the interface identifier, a calling mode of the target interface; determining, according to the calling mode and the interface parameter, a first parameter in an input parameter of the target interface function corresponding to the target interface; Calling the request identifier of the interface call request and the first parameter as input parameters of the target interface function, calling the target interface function; and obtaining an output parameter returned after calling the target interface function, where the output parameter includes the Determining the identifier and the second parameter; and returning, according to the second parameter, the result of the call of the interface call request corresponding to the request identifier to the client script. By adopting the embodiment of the present invention, through the design of the normalized interface function and the interface call, the browser can adopt a unified interface calling method to implement the call of the client script to any extended interface. Therefore, when a developer develops an extension interface, it is only necessary to develop an interface function corresponding to the extension interface to improve development efficiency.

Referring to FIG. 2, FIG. 2 is another schematic flowchart of an interface calling method according to an embodiment of the present invention. In the embodiment of the present invention, the method may include the following steps.

S201: Receive an interface call request, where the interface call request carries an interface identifier and an interface parameter corresponding to the target interface that the client script needs to invoke.

S202: Determine, according to the interface identifier, a calling manner of the target interface.

In a specific implementation, the calling interface to be called is determined according to the interface call request, and the calling mode of the target interface is determined, and the calling manner includes a synchronous call and an asynchronous call. Generally, the interface information of each interface is pre-stored in the interface database, and the interface information includes an interface identifier and a calling mode. When the browser receives the interface call request, the interface identifier is used to query the interface information corresponding to the interface identifier, and the interface information includes the interface identifier and the calling mode, and the interface information is included in the interface database. The calling mode corresponding to the interface identifier is determined as the calling mode of the target interface. Certainly, the calling mode of the target interface may also be calibrated in the interface parameter of the interface call request when the client script calls the target interface. Specifically, the embodiment of the present invention is not limited.

However, as a preferred implementation manner, determining the calling mode of the target interface may be: querying, according to the interface identifier, the interface information corresponding to the interface identifier from the preset interface database, where the interface information includes the interface identifier and the calling mode; The calling mode corresponding to the interface identifier that is queried in the interface database is determined as the calling mode of the target interface.

S203: Determine, according to the calling manner and the interface parameter, a first parameter in an input parameter of a target interface function corresponding to the interface identifier.

In the embodiment of the present invention, the asynchronous call requires the client script to carry a parameter identifying the callback function in the interface parameter. For convenience of description, the parameter identifying the callback function is referred to as a preset parameter. For example, the last parameter in the interface parameter of the asynchronous call may be used to store the preset parameter. Of course, the preset parameter may be set to other positions in the interface parameter according to a pre-agreed. In an implementation manner, if it is determined that the calling mode is an asynchronous call, the preset parameter that identifies the callback function in the interface parameter is obtained, and the callback information is saved in a preset callback database, where the callback information includes the request identifier and The callback function identified by the preset parameter, of course, the callback information may further include other information such as an environment variable required to run the callback function, and the embodiment of the present invention is not limited. Therefore, when the subsequent step (for example, step S208) returns the result of the asynchronous call, the target callback function corresponding to the request identifier is queried from the callback database according to the request identifier in the output parameter returned after the target interface function is called.

As an example, a script representing a synchronous call and an asynchronous call may be as shown in code 1 in the above embodiment. It can be seen that the interface parameters synchronously called are the parameters required by the target interface function corresponding to the target interface, and the preset parameters (callback) used to represent the callback function in the interface parameters of the asynchronous interface are not required in the target interface function corresponding to the target interface. However, after the target interface function finishes running, you need to call the callback function represented by the preset parameter to return the call result. In the embodiment of the present invention, the first parameter in the input parameter of the target interface function corresponding to the target interface is determined according to the calling mode of the target interface and the interface parameter. In the specific implementation, if the calling mode is a synchronous call, the interface parameter carried in the interface call request is determined as the first parameter in the input parameter of the target interface function corresponding to the target interface; if the calling mode is asynchronous, the interface call request is carried. The other parameters of the interface parameter except the preset parameter are determined as the first parameter of the input parameter of the target interface function, wherein the preset parameter is used to identify a callback function, and each preset parameter corresponds to a callback function.

S204: Perform format conversion on the first parameter, and the data type of the converted first parameter is a preset second data type.

Since most browsers today are multi-core browsers, that is, two or more browser kernels are included in the browser, the existing methods are designed for each browser kernel when developing an extension interface for a multi-core browser. An interface function that is the same as the function to be implemented by the extension interface not only has high development cost, but also because different browser kernels have different design specifications for interface functions, and different browser kernels identify interface functions called for the same interface identifier. Differently, the interface calling process is complicated, and thus the calling interface is inefficient.

In the embodiment of the present invention, the design of the interface function is standardized, and the interface module is designed using the same specification regardless of the browser kernel. For example, the design specification of the interface function can be as shown in the code 2. When adding the interface function, the developer only needs to implement the corresponding function according to the specification. It is worth noting that the code 2 is merely an example, and the present invention is not limited to this example.

/ / Interface function specification, id represents the request identifier corresponding to the interface call request, kv_map saves the parameters passed in the script

Value InterfaceFunction(int id,KeyValueMap kv_map);

In the specification, the id is a request identifier for tracking the interface call request and the call result; the data type of the first parameter kv_map of the interface function is a preset second data type, and the second data type may be a predefined The type of data structure used to accept any type of data, or a generic data type in a database that comes with the programming language, which can receive data of any data type. For example, the KeyValueMap type or the Value type is not limited in the embodiment of the present invention. For convenience of description, the embodiment of the present invention takes the second data type as the KeyValueMap type as an example, but it should be noted that the second data type is not limited to the KeyValueMap type. Among them, KeyValueMap or Value is a data type, like a storage box, can be used to store a variety of different types of data, such as: integers, floating-point numbers, strings, and so on. Specifically, the KeyValueMap is a key-value mapping table, and the mapping table stores a one-to-one correspondence between a key and a value. The key can be a number (the order of the parameters) ) or string (the name of the parameter), the value (Value) is the specific value of a key in the parameter.

In the embodiment of the present invention, the determined first parameter is format converted, and the data type of the converted first parameter is a preset second data type. That is, before calling the target interface function corresponding to the target interface, it is necessary to convert the first parameter passed in by the script, such as converting the first parameter into a KeyValueMap object.

For convenience of description, suppose the client script wants to call an interface that adds the history of the webpage, and the calling mode of the interface is asynchronous, the interface specification provided by the client script may be: function recordHistory(url,date,callback), One parameter indicates the URL of the incoming web page (url, assumed to be http:\\www.liebao.cn), and the second parameter indicates the time that the incoming access is required (time, assumed to be 2014-07-20 20:00) : 00), the last parameter is a script function object, the parameter is not used as a parameter of the calling interface function, but is used to notify the script after the interface function is successfully operated. Therefore, the first parameter determined according to the interface parameter in step S103 does not include This parameter. After the first parameter is converted, the first parameter of the converted KeyValueMap type is as shown in Table 2. Table 2 is a schematic diagram of a second data type provided by the embodiment of the present invention.

Table 2

Therefore, after ensuring that different browser kernels receive the interface call request of the client script, the step can be adopted. Converting the first parameter to the same data type parameter, the data type of the input parameter of the interface function is unified. Therefore, developers only need to design an interface function when developing a set of interfaces for the multi-core browser.

S205: Call the request identifier of the interface call request and the first parameter as an input parameter of the target interface function, and invoke the target interface function.

In a specific implementation, before the target interface function is invoked by using the request identifier of the interface call request and the first parameter as an input parameter of the target interface function, the request identifier of the interface call request may be determined. Considering that in the process of loading the webpage, the browser may handle multiple interface call requests at the same time. Therefore, the request identifier is used to calibrate each interface call request of the client script call interface, and the request identifier corresponds to the corresponding interface call. All the requested information is associated, the information includes the interface identifier of the interface call request, the interface parameter, the call result, and the like, so that each interface call request and the call result are tracked by the request identifier. In the embodiment of the present invention, after receiving the interface call request, determining the request identifier of the interface call request, where the request identifier may be automatically allocated when the browser kernel receives the interface call request. It can be seen that a request identifier uniquely aligns an interface call request, and the request identifier is associated with an interface identifier and an interface parameter carried in the interface call request.

Generally, after the developer develops a set of extended interfaces, the related information of the interface is saved in a preset interface database, where the interface related information includes an interface identifier and an interface function, and the interface identifier may be an interface name. If the developer has provided the target interface specified by the interface call request, the interface identifier carried in the interface call request can find a unique interface function matching the interface identifier in the preset information base. In the embodiment of the present invention, according to the interface identifier carried in the interface call request, whether the interface function matching the interface identifier exists in the interface database is queried. If yes, the browser provides the target interface specified by the interface identifier, and searches for the target interface function according to the request identifier corresponding to the interface call request and the converted first parameter; if not, the browser does not provide the target interface function. The target interface returns the default error message.

If the target interface function matching the interface identifier exists in the interface database, the request identifier and the first parameter converted in step S204 are used as input parameters of the found target interface function, and the target interface function is invoked. In other words, the request identifier and the converted first parameter are substituted into the found target interface function, and the found target interface function is run or executed. Therefore, for different browser kernels, after adopting the embodiment of the present invention, a unified specification call interface function can be adopted, and different browser kernels call the interface in the same manner, the efficiency of calling the interface is high, and the execution efficiency of the webpage is also improved.

S206: Obtain an output parameter that is returned after the target interface function is invoked, where the output parameter includes the request identifier and a second parameter, and the data type of the output parameter is a preset first data type.

After the target interface function corresponding to the target interface is invoked, the output parameter returned after the target interface function is invoked is obtained, where the output parameter includes the request identifier and the second parameter, and the data type of the output parameter is a preset first Data class Type, where the second parameter is used to represent the result of the operation of the target interface function. In a specific implementation, the first data type may be a predefined data type for accepting any type of data, or may be a general data type in a database that is included in the programming language, and the data type may receive data of any data type. . For example, the KeyValueMap type or the Value type is not limited in the embodiment of the present invention. For convenience of description, the code 2 or the embodiment of the present invention takes the first data type as the Value type as an example, but the embodiment of the present invention does not limit the first data type to the Value type. Therefore, when developers develop extension interfaces for different browser kernels, they only need to design an interface function according to the specification. It is not necessary to design an interface function for different browser kernels, and there is no need to design the interface method corresponding to the interface function. Not only can it reduce development costs, but also improve development efficiency.

It should be noted that, in a specific implementation, the data type of the second parameter may be a preset first data type, and the data type of the output parameter of the interface function is a structure, and the structure includes a request identifier and a second parameter. . For example, taking the first data type as the Value type as an example, the specification of the structure can be as shown in the code 3.

Code 3

S207: Perform format conversion on the second parameter, and the data type of the converted second parameter is a preset third data type.

As a preferred implementation manner, the second parameter in the output parameter returned after the acquired target interface function is formatted, and the data type of the converted second parameter is a preset third data type. The third data type may be a pre-defined data structure type for accepting any type of data, or may be a general data type in the client-side scripting language, for example, an Object object. Specifically, the embodiment of the present invention is not limited. Thus, the result of the call returned to the client script is normalized to improve the execution efficiency of the script. It should be noted that the format conversion may not be performed for the second parameter, and the step S208 is performed by skipping this step.

S208: Return, according to the second parameter, a call result of the interface call request corresponding to the request identifier to the client script.

The second parameter is returned to the client script as a result of the call of the interface call request corresponding to the request identifier in the output parameter according to the calling mode of the target interface. In a specific implementation, if the calling mode of the target interface is a synchronous call, the second parameter or the formatted second parameter is returned to the client script as the calling result of the interface call request corresponding to the request identifier; The calling mode is an asynchronous call, and the request identifier is determined according to the request identifier. The target target callback function takes the second parameter or the formatted second parameter as an input parameter of the target callback function, runs the target callback function to obtain an output result, and further calls the output result as the interface. The result of the requested call is returned to the client script.

In an embodiment, if the calling mode is an asynchronous call, the manner of determining the target callback function corresponding to the request identifier may be: querying, according to the request identifier, a callback corresponding to the request identifier from the callback database Information; the callback function specified by the callback information is determined as a target callback function. At the same time, if the callback information is stored with other information for running the target callback function, the current environment variable is set according to the information to ensure that the target callback function is normally run, and the result of the call is notified to the client script.

As a feasible implementation manner, after the result of the call is returned to the client script, the callback information corresponding to the request identifier in the callback database is deleted. Thereby, the amount of data is reduced, and the query efficiency of the target callback function is improved.

The following is an embodiment of the device of the present invention. The device embodiment of the present invention is the same as the method embodiment of the present invention, and is used to perform the method described in the method embodiment of the present invention. For the convenience of the description, the device embodiment of the present invention only shows a part related to the device embodiment of the present invention. For details of the technical details, please refer to the description of the method embodiment of the present invention, and details are not described herein again.

Referring to FIG. 3, FIG. 3 is a schematic structural diagram of an interface invoking device according to an embodiment of the present invention. In the embodiment of the present invention, the device may include: a receiving module 101, a mode determining module 102, a parameter determining module 103, and a call. Module 104, acquisition module 105, and return module 106.

The receiving module 101 is configured to receive an interface call request, where the interface call request carries an interface identifier and an interface parameter corresponding to a target interface that is required to be invoked by the client script, where the target interface is any one of the extended interfaces provided by the browser. extension port.

The mode determining module 102 is configured to determine, according to the interface identifier, a calling manner of the target interface.

The parameter determining module 103 is configured to determine, according to the calling manner and the interface parameter, a first parameter in an input parameter of a target interface function corresponding to the target interface.

The calling module 104 is configured to invoke the target interface function by using the request identifier of the interface call request and the first parameter as an input parameter of the target interface function.

The obtaining module 105 is configured to obtain an output parameter returned after the target interface function is invoked, where the output parameter includes the request identifier and the second parameter.

The returning module 106 is configured to return, according to the second parameter, a call result of the interface call request corresponding to the request identifier to the client script.

In the interface invoking device described in the embodiment of the present invention, an interface call request is received, where the interface call request carries an interface identifier and an interface parameter corresponding to a target interface that the client script needs to invoke, and the target interface is provided by the browser. Determining, according to the interface identifier, a calling mode of the target interface; determining, according to the calling mode and the interface parameter, a first parameter in an input parameter of the target interface function corresponding to the target interface; Calling the request identifier of the interface call request and the first parameter as input parameters of the target interface function, calling the target interface function; and obtaining an output parameter returned after calling the target interface function, where the output parameter includes the Determining the identifier and the second parameter; and returning, according to the second parameter, the result of the call of the interface call request corresponding to the request identifier to the client script. By adopting the embodiment of the present invention, through the design of the normalized interface function and the interface call, the browser can adopt a unified interface calling method to implement the call of the client script to any extended interface. Therefore, when a developer develops an extension interface, it is only necessary to develop an interface function corresponding to the extension interface to improve development efficiency.

Referring to FIG. 4, FIG. 4 is another schematic structural diagram of an interface invoking device according to an embodiment of the present invention. In the embodiment of the present invention, the device may include: a receiving module 201, a mode determining module 202, and a parameter determining module 203. The calling module 204, the obtaining module 205, the returning module 206, the first converting module 207, the second converting module 208, the saving module 301, and the deleting module 302.

The receiving module 201 is configured to receive an interface call request, where the interface call request carries an interface identifier and an interface parameter corresponding to the target interface that the client script needs to invoke, and the target interface is one of the extended interfaces provided by the browser.

The mode determining module 202 is configured to determine, according to the interface identifier, a calling manner of the target interface.

The parameter determining module 203 is configured to determine, according to the calling manner and the interface parameter, a first parameter in an input parameter of a target interface function corresponding to the target interface.

The calling module 204 is configured to invoke the target interface function by using the request identifier of the interface call request and the first parameter as an input parameter of the target interface function.

The obtaining module 205 is configured to obtain an output parameter returned after the target interface function is invoked, where the output parameter includes the request identifier and the second parameter.

The returning module 206 is configured to return, according to the second parameter, a call result of the interface call request corresponding to the request identifier to the client script.

In an embodiment, the data type of the output parameter is a preset first data type.

The first conversion module 207 is configured to perform format conversion on the first parameter, and the data type of the converted first parameter is a preset second data type.

The second conversion module 208 is configured to perform format conversion on the second parameter, and the data type of the converted second parameter is a preset third data type.

The saving module 301 is configured to save the callback information to the callback database if the calling mode is an asynchronous call, where the callback information includes the request identifier and a callback function identified by the preset parameter.

The deleting module 302 is configured to delete the callback information corresponding to the request identifier in the callback database.

In another embodiment, the parameter determining module 203 is specifically configured to:

In another embodiment, the return module 206 includes: a synchronous return unit 2061 and an asynchronous return unit 2062, as shown in FIG. 4a, which is a schematic structural diagram of one of the return modules provided in FIG.

The synchronization returning unit 2061, if the calling mode is a synchronous call, returning the second parameter to the client script as a result of calling the interface call request corresponding to the request identifier;

The asynchronous return unit 2062, if the calling mode is an asynchronous call, determining a target callback function corresponding to the request identifier, and using the second parameter as an input parameter of the target callback function, running the target callback function to obtain an output As a result, the output result is returned to the client script as a result of the call of the interface call request.

In another embodiment, the synchronization return unit 2061 is specifically configured to:

Querying the callback information corresponding to the request identifier from the callback database according to the request identifier;

In another embodiment, the mode determining module 202 is specifically configured to:

Referring to FIG. 5, FIG. 5 is a schematic diagram of another structure of an interface calling device according to an embodiment of the present invention. In the embodiment of the present invention, the device may include: a parameter converter 301, an interface proxy 302, and an interface forwarder 303. The interface notifier 304, the interface registrar 305, the interface database 306, and the call request database 307.

In a specific implementation, if the calling mode of the target interface specified by the interface calling instruction is an asynchronous call, the interface calling device may further include a callback database 308 and a callback 309. When adding an interface, the developer needs to provide the interface registrar 305 with the registration information such as the interface identifier and the calling mode of the interface. For convenience of explanation, the interface identifier is assumed to be the interface name, and the specific implementation of the interface function is provided in the main process. The interface registrar 305 records the registration information, and after the browser creates the rendering process, sends the registration information to the rendering process by means of inter-process communication, and the rendering process caches the registration information in the interface database 306, thereby, the interface database The interface information of each interface is recorded in 306. For example, the storage format of the interface database can be as shown in Table 1. The callback database 308 is configured to store the request identifier of the asynchronous call and the callback function carried in the interface call request calibrated by the request identifier when the calling mode is asynchronous, so that the callback 309 can query the callback database 308 according to the request identifier. The request identifies the corresponding target callback function, and returns the call result to the script by calling the target callback function. The call request database 307 is configured to store the requested identifier and the calling mode, so that the interface notifier 304 obtains the output parameter after the target interface function is completed, and then queries the request database 307 according to the request identifier in the output parameter. The calling mode corresponds to the calling mode. If it is a synchronous call, the output parameter is directly sent to the interface proxy 302; if it is an asynchronous call, the output parameter is sent to the callback 309. It should be noted that the interface calling device can be used in a single-process browser or in a multi-process browser, but for convenience of description, a multi-process browser is taken as an example.

Generally, the browser mostly appears as a multi-process during the running process, and the multi-process includes at least a rendering process and a main process, wherein the rendering process is used to process the rendering of the webpage content, the main process is used to process the user interface and manage all other Process Wait. Since the rendering process can only execute web pages and cannot perform other operations, the implementation of the extended interface (ie, the implementation of the interface function) must be provided in the main process. For convenience of description, assuming that the browser starts the rendering process and the main process during the running process, in the interface calling process of implementing the client script, the rendering process receives an interface call request of the client script, and the interface call request carries the client. The interface identifier and the interface parameter corresponding to the target interface that the terminal script needs to call, and the target interface is any one of the extended interfaces provided by the browser. Since the rendering process itself cannot run the target interface function corresponding to the target interface, the interface call request is reconstructed according to the interface identifier and the interface parameter passed in the client script, and the interface call request is sent to the main process, thereby, by the main process Run the interface to call the target interface function specified by the request, and return the running result to the rendering process and / or client script to implement the script call.

In the embodiment of the present invention, the parameter converter 301 receives the interface call request of the client script 201, and the interface call request carries the interface identifier and the interface parameter corresponding to the target interface that the client script 201 needs to call, and the target interface is browsed. One of the extensions provided by the device. The parameter converter 301 queries the interface database 306 for the interface information corresponding to the interface identifier. If the interface does not exist, the interface is incorrectly called, and the default error information is directly returned. If yes, the interface name corresponding to the interface identifier is determined. This interface identifies the calling mode of the corresponding target interface. Further, the first parameter in the input parameter of the target interface function corresponding to the target interface is determined according to the calling mode and the interface parameter. The parameter converter 301 performs format conversion on the first parameter, and the data type of the converted first parameter is a preset second data type, for example, a KeyValueMap type or a Value type.

The interface proxy 302 (Interface Proxy) obtains the call information required for the interface call request from the parameter converter 301, or the parameter converter 301 sends the call information to the interface proxy 302, where the call information includes the request identifier of the interface call request, The interface name, the first parameter, and the calling mode. If the calling mode is asynchronous, the calling information further includes a callback function. Of course, the request identifier may also be determined or generated by the interface proxy 302. Specifically, the embodiment of the present invention is not limited. If the calling mode is an asynchronous call, the interface proxy 302 adds the request identifier and the callback function corresponding to the request identifier to the callback database 308 according to the acquired call information. After the caller 309 receives the output parameter of the target interface function returned by the interface notifier 304 in the main process, the target callback function corresponding to the request identifier is queried from the callback database 308 according to the request identifier in the output parameter. At the same time, the interface proxy 302 sends an interface call request to the interface forwarder 303 located in the main process, which may be as shown in code 4.

For example, if the calling interface to be called is called asynchronously, assuming the interface name of the target interface is recordHistory, the code of the client script calling the target interface can be: recordHistory('http:\\www.liebao.cn' , '2014-07-20 20:00:00', onRecordHistoryDone), we can see that the first parameters include "http:\\www.liebao.cn", "2014-07-20 20:00:00", callback function The function name is onRecordHistoryDone. Therefore, the parameter converter 301 receives the interface call request of the client script to call the target interface recordHistory, determines the request identifier of the interface call request, and the calling mode of the target interface; And calling the mode and the interface parameter to determine a first parameter of the input parameter of the target interface function corresponding to the target interface. The parameter converter 303 performs format conversion on the first parameter, and the first parameter after the format conversion can be as shown in Table 2. The interface proxy 302 can add information such as a request identifier (request_id) identifying the interface call request, a callback function object (here, the onRecordHistoryDone function), and an environment variable required to normally execute the callback function to the callback database 308, ensuring that the callback can The result of the call is successfully returned to the script based on the information stored in the callback database 308. At the same time, the interface proxy 302 reconstructs the interface call request according to the acquired call information, and sends the interface call request to the interface forwarder 303 in the browser main process by means of inter-process communication. The call request of the interface may be like a code. As shown in FIG. 4, the call request of the interface may carry a request identifier request_id, an interface name interface, a first parameter arguments, and a call mode sync, where the data type of the first parameter is a preset second data type.

The code 4 describes the call request of the asynchronous interface. The request_id is used to identify the interface call request, the interface indicates that the interface identifier corresponding to the target interface is to be called, and the argument type obtained by the parameter converter 301 is preset. The first parameter of the first data type, sync is used to indicate the calling mode of the target interface.

Code 4

If the target interface to be called is a synchronous interface, the parameter sync in the interface call request is true. Similarly, the interface proxy 302 sends the call request of the constructed interface to the interface in the browser main process by means of inter-process communication. Transponder 303. If the calling mode is a synchronous call, after the interface proxy 302 sends a call request to the interface forwarder 303, the interface proxy 302 suspends execution until the browser main process finishes executing and passes the return value. If the calling mode is an asynchronous call, after the interface proxy 302 sends the call request to the interface forwarder 303, the interface proxy 302 returns immediately, so that the rendering process can continue to perform other operations, and the execution efficiency of the webpage is high.

After receiving the call request sent by the interface proxy, the interface forwarder 303 adds the request identifier and the calling manner that identifies the call request to the call request database 307 according to the call information carried in the call request, thereby being located in the main process. The call request database 307 stores the correspondence between each request identifier and the calling mode of the target interface specified by the call request. The interface forwarder 303 queries the interface registrar 305 to query the target interface function corresponding to the interface name, obtains the location of the target interface function 401 corresponding to the target interface, and uses the request identifier request_id and the first parameter argument as the queried query. The input parameter of the target interface function 401 is called, and the implementation of the target interface function may be an asynchronous implementation or a synchronous implementation.

Usually, after the interface function is finished, it needs to return the running result, such as whether the operation is successful, the data to be read, etc., and the data is the output parameter of the interface function, and the data type of the output parameter is the preset first data type. Such as KeyValueMap type or Value type. Then, after the execution of the target interface function, the output parameter is passed to the interface notifier 304, where the output parameter includes the request identifier and the second parameter, and the second parameter is the call result of the interface call request corresponding to the request identifier. Thus, the interface notifier 304 looks up the corresponding call request and calling mode in the call request database 307 according to the request identifier.

If the calling mode is a synchronous call, the interface notifier 304 sends the request identifier and the second parameter to the interface proxy 302, so that the interface proxy 302 continues to perform other operations after receiving the output parameter of the target interface function returned by the interface notifier 304. . The parameter converter 301 performs format conversion on the second parameter of the output parameter, and the data type of the converted second parameter is a preset third data type, for example, an Object object inside the script, and further, returns a corresponding identifier of the request identifier. The result is called to the script and the synchronous call is completed. After the synchronization call is completed, the corresponding item in the call request database 307 is deleted according to the request identifier, thereby reducing the amount of data and improving the query efficiency.

If the calling mode is a synchronous call, the interface proxy 302 will return to the interface forwarder 303 after sending the call request of the interface, and continue to execute other parts of the script. The return result of the calling interface needs to be returned by calling the callback function specified by the request. Therefore, the interface notifier 304 sends the request identifier and the second parameter to the callback 309 in the rendering process after the asynchronous call is made to the target interface corresponding to the request identifier from the call request database 307 according to the request identifier in the output parameter. The caller 309 uses the request identifier to query the target callback function corresponding to the request identifier from the callback database 308, and at the same time, invokes the parameter converter 301 to format convert the second parameter, and the data type of the converted second parameter is preset. The third data type, for example, the Object object of the script, uses the converted second parameter as an input parameter of the target callback function, runs the target callback function provided by the script, and returns the result of the call, and the asynchronous interface call is completed. After the asynchronous call is completed, the corresponding items in the call request database 307 and the callback database 308 are deleted according to the request identifier, thereby reducing the amount of data and improving the query efficiency.

In the interface invoking device described in the embodiment of the present invention, an interface call request is received, where the interface call request carries an interface identifier and an interface parameter corresponding to a target interface that the client script needs to invoke, and the target interface is provided by a browser. Determining, according to the interface identifier, a calling mode of the target interface; determining, according to the calling mode and the interface parameter, a first parameter in an input parameter of the target interface function corresponding to the target interface; The interface calls the request identifier and the first parameter as input parameters of the target interface function, and invokes the target interface function; and obtains an output parameter returned after calling the target interface function, where the output parameter includes Determining the request identifier and the second parameter; and returning, according to the second parameter, a call result of the interface call request corresponding to the request identifier to the client script. By adopting the embodiment of the present invention, through the design of the normalized interface function and the interface call, the browser can adopt a unified interface calling method to implement the call of the client script to any extended interface. Therefore, when a developer develops an extension interface, it is only necessary to develop an interface function corresponding to the extension interface to improve development efficiency.

Referring to FIG. 6, FIG. 6 is a schematic structural diagram of a terminal according to an embodiment of the present invention. In the embodiment of the present invention, the terminal 10 includes the interface calling device as described above. In the embodiment of the present invention, the terminal may include: a smart phone, a computer, a tablet computer, a notebook computer, a palmtop computer, and a terminal device such as a mobile Internet device (MID) or a PAD. Specifically, the embodiment of the present invention is not limited.

It is to be noted that the terminal 10 includes any interface calling device as described above, and the terminal receives an interface call request, where the interface call request carries an interface identifier and an interface parameter corresponding to the target interface that the client script needs to invoke. The target interface is one of the extended interfaces provided by the browser; determining the calling mode of the target interface according to the interface identifier; determining the input of the target interface function corresponding to the target interface according to the calling mode and the interface parameter a first parameter of the parameter; calling the request identifier of the interface call request and the first parameter as an input parameter of the target interface function, calling the target interface function; and obtaining an output returned after calling the target interface function a parameter, the output parameter includes the request identifier and the second parameter; and based on the second parameter, returning an invocation result of the interface call request corresponding to the request identifier to the client script. By adopting the embodiment of the present invention, through the design of the normalized interface function and the interface call, the browser can adopt a unified interface calling method to implement the call of the client script to any extended interface. Therefore, when a developer develops an extension interface, it is only necessary to develop an interface function corresponding to the extension interface to improve development efficiency.

Referring to FIG. 7, FIG. 7 is a schematic structural diagram of an interface calling apparatus according to an embodiment of the present invention, for performing an interface calling method disclosed in an embodiment of the present invention, where the apparatus may include: at least one processor 401, for example, The CPU, at least one network interface 404 or other user interface 403, memory 405, at least one communication bus 402. Communication bus 402 is used to implement connection communication between these components. The user interface 403 can optionally include a USB interface and other standard interfaces and wired interfaces. Network interface 404 can optionally include a Wi-Fi interface as well as other wireless interfaces. The memory 405 may include a high speed RAM memory and may also include a non-volatile memory such as at least one disk memory. The memory 405 can optionally include at least one located far from the foregoing The storage device of the processor 401. As shown in FIG. 7, an operating system 4051 and an application 4052 may be included in the memory 405 as a computer storage medium.

In some implementations, the memory 405 stores the following elements, executable modules or data structures, or a subset thereof, or their extension set:

An operating system 4051, including various system programs for implementing various basic services and processing hardware-based tasks;

The application 4052 includes various setting programs of a data block parameter setting program of the target network data, a partitioning program of the target data block, a comparison program of the target data block and the data block in the database, and a deletion program of the target data block, and the like. To achieve a variety of application services.

Specifically, the processor 401 is configured to invoke a program stored in the memory 405 to perform the following operations:

Determining, according to the calling manner and the interface parameter, a first parameter in an input parameter of a target interface function corresponding to the target interface;

In an embodiment, the data type of the output parameter is a preset first data type;

After the processor 401 performs the operation of determining the first parameter in the input parameter of the target interface function corresponding to the target interface according to the calling mode and the interface parameter, the method further includes: performing the following operations:

The processor 401 performs the obtaining the output parameter returned after the calling of the target interface function, and after the output parameter includes the operation of the request identifier and the second parameter, the method further includes:

In an embodiment, the processor 401 performs the operation of determining the first parameter of the input parameters of the target interface function according to the calling mode and the interface parameter, including: performing the following operations:

In an embodiment, the processor 401 performs the returning, according to the second parameter, a result of calling the interface call request corresponding to the request identifier to the client script, and the following operations are performed:

In an embodiment, after the performing, by the processor 401, the operation of determining the calling manner of the target interface according to the interface identifier, the method further includes:

The processor 401 performs the operation of determining the target callback function corresponding to the request identifier, including performing the following operations:

In an embodiment, after the processor 401 performs the operation of returning the second parameter as the result of the call of the interface call request corresponding to the request identifier to the client script, the method further includes:

In an embodiment, the processor 401 performs an operation of determining a calling manner of the target interface according to the interface identifier, including performing the following operations:

In the technical solution described in the embodiment of the present invention, an interface call request is received, where the interface call request carries an interface identifier and an interface parameter corresponding to a target interface that the client script needs to invoke, and the target interface is an extension provided by the browser. Determining, according to the interface identifier, a calling mode of the target interface; determining, according to the calling mode and the interface parameter, a first parameter in an input parameter of the target interface function corresponding to the target interface; Calling the requested identifier of the interface and the first parameter as input parameters of the target interface function, and calling the target interface function; Obtaining an output parameter returned after the target interface function is invoked, where the output parameter includes the request identifier and the second parameter; and returning, according to the second parameter, a call result of the interface call request corresponding to the request identifier to the Describe the client script. By adopting the embodiment of the present invention, through the design of the normalized interface function and the interface call, the browser can adopt a unified interface calling method to implement the call of the client script to any extended interface. Therefore, when a developer develops an extension interface, it is only necessary to develop an interface function corresponding to the extension interface to improve development efficiency.

In the description of the present specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" and the like means a specific feature described in connection with the embodiment or example. A structure, material or feature is included in at least one embodiment or example of the invention. In the present specification, the schematic representation of the above terms does not necessarily have to be for the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in a suitable manner in any one or more embodiments or examples. In addition, various embodiments or examples described in the specification, as well as features of various embodiments or examples, may be combined and combined.

Those skilled in the art can combine and combine the different embodiments described in the specification and the features of the different embodiments. The modules or units in all the embodiments of the present invention may be implemented by a general-purpose integrated circuit, such as a CPU (Central Processing Unit) or an ASIC (Application Specific Integrated Circuit).

The steps in the method of all the embodiments of the present invention may be sequentially adjusted, combined, and deleted according to actual needs; the modules or units in all the embodiments of the present invention may be combined, divided, and deleted according to actual needs.

Any process or method description in the flowcharts or otherwise described herein may be understood to represent a module, segment or portion of code that includes one or more executable instructions for implementing the steps of a particular logical function or process. And the scope of the preferred embodiments of the invention includes additional implementations, in which the functions may be performed in a substantially simultaneous manner or in an opposite order depending on the functions involved, in the order shown or discussed. It will be understood by those skilled in the art to which the embodiments of the present invention pertain.

The logic and/or steps represented in the flowchart or otherwise described herein, for example, may be considered as an ordered list of executable instructions for implementing logical functions, and may be embodied in any computer readable medium, Used in conjunction with, or in conjunction with, an instruction execution system, apparatus, or device (eg, a computer-based system, a system including a processor, or other system that can fetch instructions and execute instructions from an instruction execution system, apparatus, or device) Or use with equipment. For the purposes of this specification, a "computer-readable medium" can be any apparatus that can contain, store, communicate, propagate, or transport a program for use in an instruction execution system, apparatus, or device, or in conjunction with the instruction execution system, apparatus, or device. A more specific example (non-exhaustive list) of computer readable media includes the following: electrical connections having one or more wires (electrical Sub-device), portable computer case (magnetic device), random access memory (RAM), read only memory (ROM), erasable editable read only memory (EPROM or flash memory), fiber optic device, and portable CD Read only memory (CDROM). In addition, the computer readable medium may even be a paper or other suitable medium on which the program can be printed, as it may be optically scanned, for example by paper or other medium, followed by editing, interpretation or, if appropriate, other suitable The method is processed to obtain the program electronically and then stored in computer memory.

One of ordinary skill in the art can understand that all or part of the steps carried by the method of implementing the above embodiments can be completed by a program to instruct related hardware, and the program can be stored in a computer readable storage medium. When executed, one or a combination of the steps of the method embodiments is included.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. The integrated modules, if implemented in the form of software functional modules and sold or used as stand-alone products, may also be stored in a computer readable storage medium.

The above mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like. Although the embodiments of the present invention have been shown and described, it is understood that the above-described embodiments are illustrative and are not to be construed as limiting the scope of the invention. The embodiments are subject to variations, modifications, substitutions and variations.

The above is only the preferred embodiment of the present invention, and the scope of the present invention is not limited thereto, and those skilled in the art can understand all or part of the process of implementing the above embodiments, and according to the claims of the present invention. Equivalent changes made are still within the scope of the invention.

Claims

An interface calling method, comprising:

Receiving an interface call request, where the interface call request carries an interface identifier and an interface parameter corresponding to the target interface that the client script needs to call, and the target interface is one of the extended interfaces provided by the browser;

Determining, according to the interface identifier, a calling manner of the target interface;

Determining, according to the calling mode and the interface parameter, a first parameter in an input parameter of the target interface function corresponding to the interface identifier;

Calling the request identifier of the interface call request and the first parameter as input parameters of the target interface function, and calling the target interface function;

Obtaining an output parameter returned after the target interface function is invoked, where the output parameter includes the request identifier and the second parameter;

And returning, according to the second parameter, a call result of the interface call request corresponding to the request identifier to the client script.
The method according to claim 1, wherein the data type of the output parameter is a preset first data type;

After the first parameter in the input parameter of the target interface function corresponding to the target interface is determined according to the calling mode and the interface parameter, the method further includes:

Formatting the first parameter, and the data type of the converted first parameter is a preset second data type;

After the obtaining the output parameter returned after the target interface function is invoked, the method further includes:

Converting the second parameter into a format, and the data type of the converted second parameter is a preset third data type.
The method according to claim 1 or 2, wherein the determining, according to the calling mode and the interface parameter, the first parameter in the input parameter of the target interface function corresponding to the target interface comprises:

If the calling mode is a synchronous call, determining the interface parameter as the first parameter in the input parameter of the target interface function;

If the calling mode is an asynchronous call, the other parameters of the interface parameter except the preset parameter are determined as the first parameter in the input parameter of the target interface function, and the preset parameter is used to identify the callback function.
The method according to any one of claims 1 to 3, wherein the returning the call result of the interface call request corresponding to the request identifier to the client script based on the second parameter comprises:

If the calling mode is a synchronous call, the second parameter is returned to the client script as a result of the call of the interface call request corresponding to the request identifier;

If the calling mode is an asynchronous call, determining a target callback function corresponding to the request identifier, and using the second parameter as an input parameter of the target callback function, running the target callback function to obtain an output result, and then The output result is returned to the client script as a result of the call of the interface call request.
The method according to claim 4, wherein after the determining the calling mode of the target interface according to the interface identifier, the method further includes:

If the calling mode is an asynchronous call, the callback information is saved in the callback database, where the callback information includes the request identifier and a callback function identified by the preset parameter;

Determining the target callback function corresponding to the request identifier, including:

If the calling mode is an asynchronous call, query the callback information corresponding to the request identifier from the callback database according to the request identifier;

The callback function specified by the callback information is determined as a target callback function.
The method according to claim 5, wherein after the returning the second parameter as the result of the call of the interface call request corresponding to the request identifier to the client script, the method further includes:

Deleting the callback information corresponding to the request identifier in the callback database.
The method according to any one of claims 1 to 6, wherein the determining the calling manner of the target interface according to the interface identifier comprises:

Querying, according to the interface identifier, the interface information corresponding to the interface identifier from a preset interface database, where the interface information includes an interface identifier and a calling mode;

The calling mode corresponding to the interface identifier in the interface database is determined as the calling mode of the target interface.
An interface calling device, comprising:

a receiving module, configured to receive an interface call request, where the interface call request carries an interface identifier and an interface parameter corresponding to the target interface that the client script needs to invoke, and the target interface is one of the extended interfaces provided by the browser;

a mode determining module, configured to determine, according to the interface identifier, a calling mode of the target interface;

a parameter determining module, configured to determine, according to the calling manner and the interface parameter, a first parameter in an input parameter of a target interface function corresponding to the interface identifier;

a calling module, configured to invoke the request identifier of the interface call request and the first parameter as an input parameter of the target interface function, and invoke the target interface function;

An obtaining module, configured to obtain an output parameter returned after the target interface function is invoked, where the output parameter includes the request identifier and the second parameter;

And a returning module, configured to return, according to the second parameter, a call result of the interface call request corresponding to the request identifier to the client script.
The device according to claim 8, wherein the data type of the output parameter is a preset first data type, and the device further comprises:

a first conversion module, configured to perform format conversion on the first parameter, where the data type of the converted first parameter is a preset second data type;

The second conversion module is configured to perform format conversion on the second parameter, and the data type of the converted second parameter is a preset third data type.
The device according to claim 8 or 9, wherein the parameter determining module is specifically configured to:

If the calling mode is a synchronous call, determining the interface parameter as the first parameter in the input parameter of the target interface function;

If the calling mode is an asynchronous call, the other parameters of the interface parameter except the preset parameter are determined as the first parameter in the input parameter of the target interface function, and the preset parameter is used to identify the callback function.
The apparatus according to any one of claims 8 to 10, wherein the returning module comprises:

a synchronization return unit, configured to return the second parameter as a result of the call of the interface call request corresponding to the request identifier to the client script if the calling mode is a synchronous call;

An asynchronous return unit, configured to: if the calling mode is an asynchronous call, determine a target callback function corresponding to the request identifier, and use the second parameter as an input parameter of the target callback function, and run the target callback function to obtain The result is output, and the output result is returned to the client script as a result of the call of the interface call request.
The apparatus according to any one of claims 8 to 11, further comprising:

a saving module, configured to save the callback information to the callback database if the calling mode is an asynchronous call, where the callback information includes the request identifier and a callback function identified by the preset parameter,

The synchronous return unit is used to:

Querying the callback information corresponding to the request identifier from the callback database according to the request identifier;

The callback function specified by the callback information is determined as a target callback function.
The device of claim 12, further comprising:

And a deleting module, configured to delete the callback information corresponding to the request identifier in the callback database.
The apparatus according to any one of claims 8 to 13, wherein the mode determining module is configured to:

Querying, according to the interface identifier, the interface information corresponding to the interface identifier from a preset interface database, where the interface information includes an interface identifier and a calling mode;

The calling mode corresponding to the interface identifier in the interface database is determined as the calling mode of the target interface.
An interface calling device, comprising:

An interface registrar, configured to record registration information of the interface, where the registration information of the interface includes an interface identifier and an interface Way of use;

An interface database for storing interface information of each interface;

Calling the request database for storing the request identifier and calling mode of the call;

The parameter converter is configured to receive an interface call request of the client script, where the interface call request carries an interface identifier and an interface parameter corresponding to the target interface that the client script needs to invoke, and the target interface is an extended interface provided by the browser. Determining, according to the interface identifier, a calling mode of the target interface; determining, according to the calling mode and the interface parameter, a first parameter in an input parameter of a target interface function corresponding to the interface identifier;

An interface proxy, configured to acquire the call information required by the interface call request, where the call information includes a request identifier, an interface identifier, a first parameter, and a calling manner; and reconstruct an interface call request according to the obtained call information;

The interface forwarder receives the reconstructed interface call request sent by the interface proxy, adds a request identifier and a calling manner in the interface call request to the call request database, and queries the interface according to the interface identifier. The registrar acquires the target interface function corresponding to the interface identifier, obtains the location of the target interface function corresponding to the target interface, and uses the request identifier and the first parameter as input parameters of the queried target interface function, and invokes the Target interface function;

An interface notifier, configured to obtain an output parameter after the target interface function is completed, where the output parameter includes the request identifier and the second parameter, where the second parameter is a call result of the interface call request corresponding to the request identifier; And searching for a corresponding call request and a calling mode in the call request database according to the request identifier; and sending the output parameter to the interface proxy if the calling mode is a synchronous call.
The interface calling device of claim 15, further comprising:

a callback database, configured to store a request identifier of the asynchronous call and a callback function carried in the interface call request calibrated by the request identifier if the calling mode is an asynchronous call;

The callback is configured to query the callback database according to the request identifier to obtain a target callback function corresponding to the request identifier, and return a call result to the client script by calling the target callback function.
An interface calling device, comprising:

At least one processor;

a memory for storing instructions executable by the at least one processor;

The at least one processor is configured to:

Receiving an interface call request, where the interface call request carries an interface identifier and an interface parameter corresponding to the target interface that the client script needs to call, and the target interface is one of the extended interfaces provided by the browser;

Determining, according to the interface identifier, a calling manner of the target interface;

Determining, according to the calling mode and the interface parameter, an input parameter of a target interface function corresponding to the interface identifier The first parameter in ;

Calling the request identifier of the interface call request and the first parameter as input parameters of the target interface function, and calling the target interface function;

Obtaining an output parameter returned after the target interface function is invoked, where the output parameter includes the request identifier and the second parameter;

And returning, according to the second parameter, a call result of the interface call request corresponding to the request identifier to the client script.
A terminal characterized by comprising the interface calling device according to any one of claims 8-17.
A computer readable storage medium having instructions stored therein, the terminal executing the interface calling method of any one of claims 1-7 when the processor of the terminal executes the instructions.
A computer program that, when run on a processor, performs the interface invocation method of any one of claims 1-7.