CN103345420A - Method for massively calling API interfaces, system for massively calling API interfaces and device for massively calling API interfaces - Google Patents
Method for massively calling API interfaces, system for massively calling API interfaces and device for massively calling API interfaces Download PDFInfo
- Publication number
- CN103345420A CN103345420A CN2013102178324A CN201310217832A CN103345420A CN 103345420 A CN103345420 A CN 103345420A CN 2013102178324 A CN2013102178324 A CN 2013102178324A CN 201310217832 A CN201310217832 A CN 201310217832A CN 103345420 A CN103345420 A CN 103345420A
- Authority
- CN
- China
- Prior art keywords
- call
- batch
- acting server
- api
- array
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Abstract
The invention provides a method for massively calling API interfaces. The method comprises the following steps that a third-party application client obtains address calling information and parameter calling information of multiple API interfaces, and the request for massive calling is sent to a proxy server, wherein the request for massive calling comprises a meta-information array composed of the address calling information and the parameter calling information of the API interfaces; the proxy server obtains multiple corresponding return results from the API interfaces according to the meta-information array; the proxy server gathers the return results and sends the return results to the third-party application client. The method for massively calling the API interfaces is short in calling time, strong in universality, optimized in performance and good in user experience. The invention further discloses the method for massively calling the API interfaces, the third application client and the proxy server.
Description
Technical field
The present invention relates to field of computer technology, particularly a kind of batch calls the mthods, systems and devices of api interface.
Background technology
Many open platforms have appearred in the continuous development along with Internet technology.Software systems in the open platform are by disclose its application programming interface (API) or function (function), make the program of outside can increase the function of these software systems or use the resource of these software systems.Be present popular platform as Baidu's open platform, Tengxun's open platform, Sina's microblogging open platform etc.The Open api interface that most of main flow open platforms provide is based on the http/https agreement, and for improving safety, increasing open platform begins to adopt the Open api interface specification based on the https agreement.
Generally speaking, the third party uses, and comprise client and service end, and Open api interface service provider generally can be in same Intranet environment.Therefore, the third party uses the Open api interface that at every turn calls a platform side all needs to carry out a public network http/https request.Because the network speed of public network is generally all lower, average level arrives between several M at several K, therefore most of consumption on public network http/https connection, public network data transmission of stand-by period really consumes in the time that the interface business of platform side's service end is handled and then only accounts for one of them very little ratio.When needing to call repeatedly in the business processing process that the third party uses or during a plurality of Open api interface, waiting for that the time proportion that network connection and data transmission consume can be very big, become the bottleneck that self performance and user's experience are used in influence.For mobile application the among the slower mobile network of speed, this problem is then more serious.
Particularly, for calling of a plurality of Open api interfaces that do not call the sequential requirement, for example call the A interface earlier and call B interface again and call B interface earlier and call the A interface again and handle not influence for applied business, the mode that third party's application end can be by concurrent invocation is to reduce the network stand-by period.But for most of programming languages, realize that the difficulty of concurrent request itself is bigger, have higher requirement for the technical capability of application developer.For calling of a plurality of Open api interfaces that have the sequential called to require, for example call the A interface earlier and call B interface again and call B interface earlier that to call the A interface more influential for applied business, third party's application end can not be carried out concurrent invocation, can only serial call, in this case, relying on application end self is to optimize performance.The no context data dependence relation refers to not exist and calls the A interface earlier, and then calls the situation of B interface according to the return data of A interface.
At present in the technology, in order to reach the performance of the Open api interface that promotes third party's application call platform side, active platform can provide the api interface of some customizations specially, and function is with to call the function that a plurality of general api interfaces commonly used realize the same, but the following shortcoming of the method:
(1), too customize, can't be general.For example customize an api interface that is ABC, to realize successively calling simultaneously the function of A, B, these 3 api interfaces of C, this ABC interface can't realize only calling the function of A and two interfaces of B, also can't realize calling the function of A, B, these 4 interfaces of C, D.
(2), the cost of development height, with method for customizing, realize calling the quantity of the api interface of the function that a plurality of api interfaces can realize, can reach at most 2! + 3! + ...+N! Individual, wherein, the quantity of the general api interface that N provides for platform side.
Summary of the invention
The present invention is intended to solve at least one of technical matters that exists in the prior art.
For this reason, one object of the present invention is to propose the method that a kind of batch calls api interface, and allocating time is shorter, highly versatile, and performance has obtained optimization, and the user experiences.
Second purpose of the present invention is to propose the system that a kind of batch calls api interface.
The 3rd purpose of the present invention is to propose a kind of third party's application end.
The 4th purpose of the present invention is to propose a kind of acting server.
For achieving the above object, the embodiment of first aspect present invention has proposed the method that a kind of batch calls api interface, may further comprise the steps: third party's application end is obtained call address information and the call parameters information of a plurality of api interfaces, and to acting server transmission batch call request, wherein, described batch call request comprises the metamessage array that call address information and call parameters information by a plurality of api interfaces constitute; Described acting server obtains corresponding a plurality of return results according to described metamessage array from described a plurality of api interfaces; Described acting server gathers described a plurality of return results and is sent to described third party's application end.
The method of calling api interface according to the batch of the embodiment of the invention can promote the performance that a plurality of Open api interfaces that the third party uses the no context data dependence relation in the same service request call, allocating time is short, relatively flexibly, and highly versatile, promoted the performance that the third party uses, and improved third party developer and used the user of the Open api interface of open platform to experience.
In one embodiment of the invention, also comprise: the requirement that described third party's application end is called according to described batch is added in described batch call request and is called gomma.
In one embodiment of the invention, also comprise: described acting server obtains corresponding invocation pattern according to calling gomma, and obtains corresponding a plurality of return results according to invocation pattern and the described metamessage array of described correspondence from described a plurality of api interfaces.
In one embodiment of the invention, do not call gomma when described batch call request comprises, described acting server calls with the concurrent invocation pattern; Call gomma when described batch call request comprises, described acting server calls with the serial invocation pattern according to the order of described a plurality of api interfaces in described metamessage array.Concurrently can save allocating time, raise the efficiency, thereby performance is optimized.
In one embodiment of the invention, also comprise: described acting server is a plurality of Intranet call address information with the call address information translation of described a plurality of api interfaces.
In one embodiment of the invention, described acting server gathers described a plurality of return results and is sent to described third party's application end and further comprises: described acting server is described to generate a plurality of description results with the return results of described a plurality of api interfaces with default form.
In one embodiment of the invention, also comprise: call gomma when described batch call request comprises, described acting server is put into described a plurality of description results to a JSON array or XML object according to the order of described a plurality of api interfaces in described metamessage array, and described JSON array or XML object are fed back to described third party's application end.
In one embodiment of the invention, described call parameters information comprises parameter list that api interface imports into, calls the employed HTTP method of api interface.
The embodiment of second aspect present invention has proposed the system that a kind of batch calls api interface, comprise third party's application end, acting server and at least one API service end, wherein, described third party's application end, be used for obtaining call address information and the call parameters information of a plurality of api interfaces, and to described acting server transmission batch call request, wherein, described batch call request comprises the metamessage array that is made of the call address information of a plurality of api interfaces and call parameters information; Described acting server is used for obtaining corresponding a plurality of return results according to described metamessage array from described a plurality of api interfaces, and described a plurality of return results are gathered and are sent to described third party's application end; Described at least one API service end is used for providing described a plurality of api interface.
The system of calling api interface according to the batch of the embodiment of the invention can promote the performance that a plurality of Open api interfaces that the third party uses the no context data dependence relation in the same service request call, allocating time is short, relatively flexibly, and highly versatile, promoted the performance that the third party uses, and improved third party developer and used the user of the Open api interface of open platform to experience.
In one embodiment of the invention, described third party's application end, the requirement that also is used for calling according to described batch is called gomma in described batch call request interpolation.
In one embodiment of the invention, described acting server, also be used for obtaining corresponding invocation pattern according to calling gomma, and obtain corresponding a plurality of return results according to invocation pattern and the described metamessage array of described correspondence from described a plurality of api interfaces.
In one embodiment of the invention, wherein, do not call gomma when described batch call request comprises, described acting server calls with the concurrent invocation pattern; Call gomma when described batch call request comprises, described acting server calls with the serial invocation pattern according to the order of described a plurality of api interfaces in described metamessage array.Concurrently can save allocating time, raise the efficiency, thereby performance is optimized.
In one embodiment of the invention, described acting server, also the call address information translation that is used for described a plurality of api interfaces is a plurality of Intranet call address information.
In one embodiment of the invention, described acting server is described to generate a plurality of description results with the return results of described a plurality of api interfaces with default form.
In one embodiment of the invention, when comprising, described batch call request calls gomma, described acting server is put into described a plurality of description results to a JSON array or XML object according to the order of described a plurality of api interfaces in described metamessage array, and described JSON array or XML object are fed back to described third party's application end.
In one embodiment of the invention, described call parameters information comprises parameter list that api interface imports into, calls the employed HTTP method of api interface.
The embodiment of third aspect present invention has proposed a kind of third party's application end, comprises acquisition module, sending module and receiver module.
Wherein, acquisition module is used for obtaining call address information and the call parameters information of a plurality of api interfaces; Sending module is used for sending call request in batches to acting server, and wherein, described batch call request comprises the metamessage array that is made of the call address information of a plurality of api interfaces and call parameters information; Receiver module be used for to receive the summarized results of a plurality of return results that described acting server obtains according to described metamessage array.
Third party's application end according to the embodiment of the invention sends call request in batches to acting server, allocating time is short, highly versatile, the performance that the third party uses is better than classic method, and has improved third party developer and used the user of the Open api interface of open platform to experience.
In one embodiment of the invention, also comprise: add module and call gomma for the requirement of calling according to described batch in described batch call request interpolation.
In one embodiment of the invention, described acting server obtains corresponding invocation pattern according to calling gomma, and obtains corresponding a plurality of return results according to invocation pattern and the described metamessage array of described correspondence from described a plurality of api interfaces.
In one embodiment of the invention, described call parameters information comprises parameter list that api interface imports into, calls the employed HTTP method of api interface.
The embodiment of fourth aspect present invention has proposed a kind of acting server, comprises receiver module, acquisition module and gathering and sending module as a result.
Wherein, receiver module is used for receiving the batch call request that third party's application end sends to acting server, and wherein, described batch call request comprises the metamessage array that is made of the call address information of a plurality of api interfaces and call parameters information; Acquisition module is used for obtaining corresponding a plurality of return results according to described metamessage array from described a plurality of api interfaces as a result; Gather and sending module is used for described a plurality of return results are gathered and are sent to described third party's application end.
Acting server according to the embodiment of the invention receives call request in batches, obtain the result and be sent to third party's application end according to the metamessage array, promote the performance that a plurality of Open api interfaces that the third party uses the no context data dependence relation in the same service request call, allocating time is short, relatively flexibly, highly versatile has improved third party developer and has used the user of the Open api interface of open platform to experience.
In one embodiment of the invention, wherein, has the gomma of calling in the described batch call request.
In one embodiment of the invention, described acquisition module as a result obtains corresponding invocation pattern according to calling gomma, and obtains corresponding a plurality of return results according to invocation pattern and the described metamessage array of described correspondence from described a plurality of api interfaces.
In one embodiment of the invention, do not call gomma when described batch call request comprises, described acting server calls with the concurrent invocation pattern; Call gomma when described batch call request comprises, described acting server calls with the serial invocation pattern according to the order of described a plurality of api interfaces in described metamessage array.Concurrently can save allocating time, raise the efficiency, thereby performance is optimized.
In one embodiment of the invention, also comprise: modular converter, the call address information translation that is used for described a plurality of api interfaces is a plurality of Intranet call address information.
In one embodiment of the invention, described gather and sending module is described to generate a plurality of description results with the return results of described a plurality of api interfaces with default form.
In one embodiment of the invention, when comprising, described batch call request calls gomma, described gather and sending module is put into described a plurality of description results to a JSON array or XML object according to the order of described a plurality of api interfaces in described metamessage array, and described JSON array or XML object are fed back to described third party's application end.
In one embodiment of the invention, described call parameters information comprises parameter list that api interface imports into, calls the employed HTTP method of api interface.
Additional aspect of the present invention and advantage part in the following description provide, and part will become obviously from the following description, or recognize by practice of the present invention.
Description of drawings
Above-mentioned and/or additional aspect of the present invention and advantage are from obviously and easily understanding becoming the description of embodiment in conjunction with following accompanying drawing, wherein:
Fig. 1 is the process flow diagram that calls the method for api interface according to the batch of the embodiment of the invention;
Fig. 2 is the method detail flowchart that calls api interface according to the batch of the embodiment of the invention;
Fig. 3 is the structural representation according to the interface interchange sequential relationship comparison diagram of the embodiment of the invention;
Fig. 4 is the structural representation that calls the system of api interface according to the batch of the embodiment of the invention;
Fig. 5 is the structural representation according to third party's application end of the embodiment of the invention; With
Fig. 6 is the structural representation according to the acting server of the embodiment of the invention.
Embodiment
Describe embodiments of the invention below in detail, the example of described embodiment is shown in the drawings, and wherein identical or similar label is represented identical or similar elements or the element with identical or similar functions from start to finish.Be exemplary below by the embodiment that is described with reference to the drawings, only be used for explaining the present invention, and can not be interpreted as limitation of the present invention.
Describe the method for calling api interface according to the batch of the embodiment of the invention below with reference to Fig. 1, may further comprise the steps:
Step S110: third party's application end is obtained call address information and the call parameters information of a plurality of api interfaces, and to acting server transmission batch call request, wherein, in batches call request comprises the metamessage array that call address information and call parameters information by a plurality of api interfaces constitute.
Wherein, call parameters information comprises parameter list that api interface imports into, calls the employed HTTP method of api interface.
Can also comprise: third party's application end is added in the batch call request according to the requirement of calling in batches and is called gomma.
Step S120: acting server obtains corresponding a plurality of return results according to the metamessage array from a plurality of api interfaces.
Wherein, can also comprise that acting server obtains corresponding invocation pattern according to calling gomma, and obtain corresponding a plurality of return results according to invocation pattern and the metamessage array of correspondence from a plurality of api interfaces.
Also comprise: acting server is a plurality of Intranet call address information with the call address information translation of a plurality of api interfaces.
In one embodiment of the invention, do not call gomma when the batch call request comprises, acting server calls with the concurrent invocation pattern; Call gomma when the batch call request comprises, acting server calls with the serial invocation pattern according to the order of a plurality of api interfaces in the metamessage array.
Step S130: acting server gathers a plurality of return results and is sent to third party's application end.
Wherein, acting server gathers a plurality of return results and is sent to third party's application end and further comprises: acting server is described to generate a plurality of description results with the return results of a plurality of api interfaces with default form.
Also comprise: call gomma when the batch call request comprises, acting server is put into a plurality of description results to a JSON array or XML object according to the order of a plurality of api interfaces in the metamessage array, and JSON array or XML object are fed back to third party's application end.
With specific embodiment shown in Figure 2 this method is described in detail below, is understandable that, following description is not limited thereto according to embodiments of the invention only for illustrative purposes.
Step S210: third party's application end generates the corresponding metamessage data of interface interchange with the call address information of Open api interface, data such as the HTTP method packing of importing parameter into, should use.Particularly, third party's application end needs are carried out each Open api interface of calling in batches call address information, call the required parameter list that imports into of this api interface, call the employed HTTP method of this api interface data such as (as comprising GET, POST, DELETE, PUT etc.) and be described by default form, wherein default form comprises the object as JSON, the JSON array, forms such as XML node.Third party's application end forms the metamessage array of interface interchange request correspondence.
Step S220: whether third party's application end will need the corresponding metamessage array of calling in batches of a plurality of Open api interfaces and be used for a plurality of Open api interfaces of expression to exist the gomma information of calling the sequential requirement to be sent to the interface IP address of acting server correspondence.
Step S230: proxy server parses metamessage array, obtain a plurality of Open api interfaces call address information, import the relevant informations such as HTTP method of parameter, use into.Particularly, provide the acting server that interface calls service in batches to receive call request in batches, obtain the call address information of the Open api interface that third party's application end calls, specifically import parameter list and initiate the relevant informations such as HTTP method of call request into according to the metamessage array.
Step S240: acting server replaces to corresponding Intranet domain name or Intranet IP address with the domain name part in the call address information of api interface, to generate corresponding Intranet call address information.
Step S250: whether acting server is judged to exist between a plurality of interfaces and is called the sequential requirement.Particularly, whether acting server calls corresponding Intranet HTTP request bag data according to the information generation Open api interface that decomposes, exist the label information that calls the sequential requirement to judge according to a plurality of Open api interfaces of expression.
Step S251: if label information is represented that a plurality of Open api interfaces do not exist and called the sequential requirement, acting server calls with the concurrent invocation pattern, by concurrent operations a plurality of Intranet HTTP requests is sent on the corresponding server of each Open api interface with wrapping data parallels.Initiate N Intranet HTTP request concurrently, after referring to send the Intranet HTTP request bag of an interface correspondence, begin to send the corresponding Intranet HTTP request of next interface bag immediately, asking bag all to send up to the Intranet HTTP of all N interface finishes, just begin to receive the return results of each interface, till the return results of all N interface all is received.
Step S252: call the sequential requirement if label information is represented a plurality of Open api interfaces existence, then according to the arrangement of elements order of each Open api interface in the metamessage array, initiate the corresponding Intranet HTTP request of each Open api interface serially successively.Initiate N Intranet HTTP request serially, after referring to send the corresponding Intranet HTTP request of an interface bag, the return results of this interface is waited for and is received on block type ground synchronously, up to receiving return results, could continue to send next interface corresponding Intranet HTTP request bag and wait for its return results packet of reception, all finish up to the Intranet HTTP of all N interface request so repeatedly.
Step S260: acting server sends Intranet HTTP request bag data to the corresponding server of Open api interface, receives the result that this server returns, and handles and be sent to third party's application end.
Interface calls the agency service end of service in batches behind the return results that receives the corresponding Intranet HTTP request of Open api interface, with the return results of each api interface with default form, as forms such as JSON object or XML nodes, be described, and put it in JSON array or the XML object according to the order of each interface in the metamessage array, and this JSON array or XML object are back to third party's application end.
Step S270: after third party's application end receives the return results of interface batch call request, according to each Open api interface putting in order in described metamessage array return results is resolved, with the corresponding return results of each Open api interface that obtains.
When needing to call the Open api interface of N no context data dependence relation in some service request processing procedures of third party's application end, use this method, N Open api interface calls the time T 1 that consumes and can calculate by following formula:
Tie-time+N interface API of tie-time+N Intranet HTTP of 1 public network HTTP/HTTPS of T1 ≈ business is wrapped and transmission time+1 a public network HTTP/HTTPS request bag of respond packet and the transmission time of respond packet in processing time+N Intranet HTTP request of server end.
Adopt traditional implementation, consumption can be calculated by following formula this N the time T that the Open api interface calls 2:
Tie-time+N interface of N public network HTTP/HTTPS of T2 ≈ is asked the transmission time of bag and respond packet at processing time+N public network HTTP/HTTPS of service end.
Because the network speed of public network is low very more than inner-mesh network speed, each interface is compared also much smaller in the processing time of server end with the transmission time of data on public network simultaneously, therefore T2/T1 is close to N, be third party when being applied in the Open api interface that calls N no context data dependence relation, the performance of using this method will have nearly N lifting doubly.
Be example as Fig. 3 for three the Open api interfaces of A, B, C with third party's application call no context data dependence relation call, contrasted the sequential relationship of calling of using this method front and back.As shown in Figure 3, a is for before using this method, and A, B, C interface are initiated request to server end successively, and accept the request of server end.B has to call the sequential relationship of using this method under the sequential situation, and A, B, three interfaces of C call in batches to acting server, and acting server initiates to ask and accept request to server according to sequential relationship successively.C does not call the sequential relationship of using this method under the sequential situation for having, and A, B, three interfaces of C call in batches to acting server, and acting server adopts the mode of concurrent invocation, initiates request to server simultaneously.Can draw the minimizing trend that obviously is total consuming time of a plurality of Open api interfaces of third party's application call among a, b, the c.
The method of calling api interface according to the batch of the embodiment of the invention is more flexible, and allocating time reduces, and has promoted the performance that the third party uses, and has improved third party developer and used the user of the Open api interface of open platform to experience.
Describe the system 100 of calling api interface according to the batch of the embodiment of the invention below with reference to Fig. 4, comprise third party's application end 110, acting server 120 and at least one API service end 130.Wherein,
Third party's application end 110 is used for obtaining call address information and the call parameters information of a plurality of api interfaces, and to acting server 120 transmission batch call request, wherein, in batches call request comprises the metamessage array that call address information and call parameters information by a plurality of api interfaces constitute; Acting server 120 is used for obtaining corresponding a plurality of return results according to the metamessage array from a plurality of api interfaces, and a plurality of return results are gathered and are sent to third party's application end 110; At least one API service end 130 is used for providing a plurality of api interfaces.
Wherein, call parameters information comprises parameter list that api interface imports into, calls the employed HTTP method of api interface.
Third party's application end 110 also is used for calling gomma according to the requirement of calling in batches in the interpolation of batch call request.
Acting server 120 also is used for obtaining corresponding invocation pattern according to calling gomma, and obtains corresponding a plurality of return results according to invocation pattern and the metamessage array of correspondence from a plurality of api interfaces.Acting server 120, also the call address information translation that is used for a plurality of api interfaces is a plurality of Intranet call address information.Acting server 120 is described to generate a plurality of description results with the return results of a plurality of api interfaces with default form.
In one embodiment of the invention, do not call gomma when the batch call request comprises, acting server 120 calls with the concurrent invocation pattern; Call gomma when the batch call request comprises, acting server 120 calls with the serial invocation pattern according to the order of a plurality of api interfaces in the metamessage array.
In one embodiment of the invention, when comprising, the batch call request calls gomma, acting server 120 is put into a plurality of description results to a JSON array or XML object according to the order of a plurality of api interfaces in the metamessage array, and JSON array or XML object are fed back to third party's application end 110.
Following specific embodiment is described in detail native system, is understandable that, following description is not limited thereto according to embodiments of the invention only for illustrative purposes.
Third party's application end 110 generates the corresponding metamessage data of interface interchange with the call address information of Open api interface, data such as the HTTP method packing of importing parameter into, should use.Particularly, third party's application end 110 needs are carried out each Open api interface of calling in batches call address information, call the required parameter list that imports into of this api interface, call the employed HTTP method of this api interface data such as (as comprising GET, POST, DELETE, PUT etc.) and be described by default form, wherein default form comprises the object as JSON, the JSON array, forms such as XML node.Third party's application end 110 forms the metamessage array of interface interchange request correspondence.Whether third party's application end 110 will need the corresponding metamessage array of calling in batches of a plurality of Open api interfaces and be used for a plurality of Open api interfaces of expression to exist the gomma information of calling the sequential requirement to be sent to the interface IP address of acting server 120 correspondences.
Acting server 120 analytical element information arrays, obtain a plurality of Open api interfaces call address information, import the relevant informations such as HTTP method of parameter, use into.Particularly, provide the acting server 120 that interface calls service in batches to receive call request in batches, obtain the call address information of the Open api interface that third party's application end 110 calls, specifically import parameter list and initiate the relevant informations such as HTTP method of call request into according to the metamessage array.Acting server 120 replaces to corresponding Intranet domain name or Intranet IP address with the domain name part in the call address information of api interface, to generate corresponding Intranet call address information.Whether acting server 120 is judged to exist between a plurality of interfaces and is called the sequential requirement.Particularly, whether acting server 120 calls corresponding Intranet HTTP request bag data according to the information generation Open api interface that decomposes, exist the label information that calls the sequential requirement to judge according to a plurality of Open api interfaces of expression.
(1) if label information represent that a plurality of Open api interfaces do not exist and call the sequential requirement, acting server 120 calls with the concurrent invocation pattern, by concurrent operations a plurality of Intranet HTTP requests is sent on the corresponding API service end 130 of each Open api interface with wrapping data parallels.Initiate N Intranet HTTP request concurrently, after referring to send the Intranet HTTP request bag of an interface correspondence, begin to send the corresponding Intranet HTTP request of next interface bag immediately, asking bag all to send up to the Intranet HTTP of all N interface finishes, just begin to receive the return results of each interface, till the return results of all N interface all is received.
(2) call the sequential requirement if label information is represented a plurality of Open api interfaces existence, then according to the arrangement of elements order of each Open api interface in the metamessage array, initiate the corresponding Intranet HTTP request of each Open api interface serially successively.Initiate N Intranet HTTP request serially, after referring to send the corresponding Intranet HTTP request of an interface bag, the return results of this interface is waited for and is received on block type ground synchronously, up to receiving return results, could continue to send next interface corresponding Intranet HTTP request bag and wait for its return results packet of reception, all finish up to the Intranet HTTP of all N interface request so repeatedly.
Acting server 120 sends Intranet HTTP request bag data to the corresponding API service end 130 of Open api interface, receives the result that this API service end 130 is returned, and handles and be sent to third party's application end 110.
Interface calls the acting server 120 of service in batches behind the return results that receives the corresponding Intranet HTTP request of Open api interface, with the return results of each api interface with default form, as forms such as JSON object or XML nodes, be described, and put it in JSON array or the XML object according to the order of each interface in the metamessage array, and this JSON array or XML object are back to third party's application end 110.
Third party's application end 110 is resolved return results according to each Open api interface putting in order in described metamessage array, with the corresponding return results of each Open api interface that obtains after receiving the return results of interface batch call request.
When needing to call the Open api interface of N no context data dependence relation in some service request processing procedures that the third party uses, use native system, N Open api interface calls the time T 1 that consumes and can calculate by following formula:
Tie-time+N interface API of tie-time+N Intranet HTTP of 1 public network HTTP/HTTPS of T1 ≈ business is wrapped and transmission time+1 a public network HTTP/HTTPS request bag of respond packet and the transmission time of respond packet in processing time+N Intranet HTTP request of server end.
Adopt traditional implementation, consumption can be calculated by following formula this N the time T that the Open api interface calls 2:
Tie-time+N interface of N public network HTTP/HTTPS of T2 ≈ is asked the transmission time of bag and respond packet at processing time+N public network HTTP/HTTPS of service end.
Because the network speed of public network is low very more than inner-mesh network speed, each interface is compared also much smaller in the processing time of server end with the transmission time of data on public network simultaneously, therefore T2/T1 is close to N, be third party when being applied in the Open api interface that calls N no context data dependence relation, the performance of using native system will have nearly N lifting doubly.
Be example as Fig. 3 for three the Open api interfaces of A, B, C with third party's application call no context data dependence relation call, contrasted the sequential relationship of calling of using the native system front and back.As shown in Figure 3, a is for before using native system, and A, B, C interface are initiated request to server end successively, and accept the request of server end.B has to call the sequential relationship of using native system under the sequential situation, and A, B, three interfaces of C call in batches to acting server 120, and acting server 120 initiates to ask and accept request to server according to sequential relationship successively.C does not call the sequential relationship of using native system under the sequential situation for having, and A, B, three interfaces of C call in batches to acting server 120, and acting server 120 adopts the mode of concurrent invocation, initiates request to server simultaneously.Can draw the minimizing trend that obviously is total consuming time of a plurality of Open api interfaces of third party's application call among a, b, the c.
The systematic comparison of calling api interface according to the batch of the embodiment of the invention is flexible, and allocating time reduces, and has promoted the performance that the third party uses, and has improved third party developer and used the user of the Open api interface of open platform to experience.
Below with reference to the third party application end 200 of Fig. 5 description according to the embodiment of the invention, comprise acquisition module 210, sending module 220, receiver module 230 and add module 240.
In one embodiment of the invention, also comprise and add module 240, be used for calling gomma according to the requirement of calling in batches in the interpolation of batch call request.
Acting server obtains corresponding invocation pattern according to calling gomma, and obtains corresponding a plurality of return results according to invocation pattern and the metamessage array of correspondence from a plurality of api interfaces.
Wherein, call parameters information comprises parameter list that api interface imports into, calls the employed HTTP method of api interface.
With specific embodiment this third party application end is described in detail below, is understandable that, following description is not limited thereto according to embodiments of the invention only for illustrative purposes.
Whether interpolation module 240 exists according to a plurality of Open api interfaces is called the gomma that sequential requirement interpolation is used for expression.
The interface IP address that sending module 220 will need the corresponding metamessage array of a plurality of Open api interfaces called in batches and gomma to be sent to the acting server correspondence.
Proxy server parses metamessage array, obtain a plurality of Open api interfaces call address information, import the relevant informations such as HTTP method of parameter, use into.Judge whether to exist between a plurality of interfaces and call the sequential requirement, Dui Ying employing concurrent invocation pattern or serial invocation pattern call respectively, acting server sends Intranet HTTP request bag data to the corresponding server of Open api interface, receive the result that this server returns, handle and be sent to third party's application end.
After acting server receives the return results of the corresponding Intranet HTTP request of Open api interface, with the return results of each api interface with default form, as forms such as JSON object or XML nodes, be described, and put it in JSON array or the XML object according to the order of each interface in the metamessage array, and this JSON array or XML object are back to third party's application end.
When needing to call the Open api interface of N no context data dependence relation in some service request processing procedures that the third party uses, according to this third party application end with and the system that forms, the time T 1 that N Open api interface calls consumption can calculate by following formula:
Tie-time+N interface API of tie-time+N Intranet HTTP of 1 public network HTTP/HTTPS of T1 ≈ business is wrapped and transmission time+1 a public network HTTP/HTTPS request bag of respond packet and the transmission time of respond packet in processing time+N Intranet HTTP request of server end.
Adopt traditional implementation, consumption can be calculated by following formula this N the time T that the Open api interface calls 2:
Tie-time+N interface of N public network HTTP/HTTPS of T2 ≈ is asked the transmission time of bag and respond packet at processing time+N public network HTTP/HTTPS of service end.
Because the network speed of public network is low very more than inner-mesh network speed, each interface is compared also much smaller in the processing time of server end with the transmission time of data on public network simultaneously, therefore T2/T1 is close to N, be third party when being applied in the Open api interface that calls N no context data dependence relation, the performance of using native system will have nearly N lifting doubly.
Be example as Fig. 3 for three the Open api interfaces of A, B, C with third party's application call no context data dependence relation call, contrasted the sequential relationship of calling of using the native system front and back.As shown in Figure 3, a is for before using native system, and A, B, C interface are initiated request to server end successively, and accept the request of server end.B has to call the sequential relationship of using native system under the sequential situation, and A, B, three interfaces of C call in batches to acting server, and acting server initiates to ask and accept request to server according to sequential relationship successively.C does not call the sequential relationship of using native system under the sequential situation for having, and A, B, three interfaces of C call in batches to acting server, and acting server adopts the mode of concurrent invocation, initiates request to server simultaneously.Can draw the minimizing trend that obviously is total consuming time of a plurality of Open api interfaces of third party's application call among a, b, the c.
According to third party's application end of the embodiment of the invention calling of a plurality of api interfaces being carried out batch calls, reduced allocating time, promoted self performance, and improved third party developer and used the user of the Open api interface of open platform to experience, brought dirigibility and optimized the space to server end.
Below with reference to Fig. 6 acting server 300 according to the embodiment of the invention is described, comprise receiver module 310, as a result acquisition module 320, gather and sending module 330 and modular converter 340.
Wherein, receiver module 310 is used for receiving the batch call request that third party's application end sends to acting server, and wherein, call request comprises the metamessage array that call address information and call parameters information by a plurality of api interfaces constitute in batches; Acquisition module 320 is used for obtaining corresponding a plurality of return results according to the metamessage array from a plurality of api interfaces as a result; Gather and sending module 330 is used for a plurality of return results are gathered and are sent to third party's application end.
Also comprise modular converter 340, the call address information translation that is used for a plurality of api interfaces is a plurality of Intranet call address information.
Wherein, has the gomma of calling in the call request in batches.Call parameters information comprises parameter list that api interface imports into, calls the employed HTTP method of api interface.
Acquisition module 320 obtains corresponding invocation pattern according to calling gomma as a result, and obtains corresponding a plurality of return results according to invocation pattern and the metamessage array of correspondence from a plurality of api interfaces.
Gather and sending module 330 is described to generate a plurality of description results with the return results of a plurality of api interfaces with default form.
In one embodiment of the invention, do not call gomma when the batch call request comprises, acting server calls with the concurrent invocation pattern; Call gomma when the batch call request comprises, acting server calls with the serial invocation pattern according to the order of a plurality of api interfaces in the metamessage array.
When comprising, the batch call request calls gomma, gather and sending module 330 is put into a plurality of description results to a JSON array or XML object according to the order of a plurality of api interfaces in the metamessage array, and JSON array or XML object are fed back to third party's application end.
With specific embodiment this acting server is described in detail below, is understandable that, following description is not limited thereto according to embodiments of the invention only for illustrative purposes.
Third party's application end generates the corresponding metamessage data of interface interchange with the call address information of Open api interface, data such as the HTTP method packing of importing parameter into, should use.Particularly, third party's application end needs are carried out each Open api interface of calling in batches call address information, call the required parameter list that imports into of this api interface, call the employed HTTP method of this api interface data such as (as comprising GET, POST, DELETE, PUT etc.) and be described by default form, wherein default form comprises the object as JSON, the JSON array, forms such as XML node.Third party's application end forms the metamessage array of interface interchange request correspondence.Whether third party's application end will need the corresponding metamessage array of calling in batches of a plurality of Open api interfaces and be used for a plurality of Open api interfaces of expression to exist the gomma information of calling the sequential requirement to be sent to the interface IP address of acting server correspondence.
Receiver module 310 receives the batch call request that third party's application end sends to acting server, acquisition module 320 analytical element information arrays as a result, obtain a plurality of Open api interfaces call address information, import the relevant informations such as HTTP method of parameter, use into.Particularly, acquisition module 320 provides the acting server that interface calls service in batches to receive call request in batches as a result, obtains the call address information of the Open api interface that third party's application end calls, specifically imports parameter list and initiate the relevant informations such as HTTP method of call request into according to the metamessage array.
Modular converter 340 replaces to corresponding Intranet domain name or Intranet IP address with the domain name part in the call address information of api interface, to generate corresponding Intranet call address information.
Whether acquisition module 320 is judged to exist between a plurality of interfaces and is called the sequential requirement as a result.Particularly, whether acquisition module 320 calls corresponding Intranet HTTP request bag data according to the information generation Open api interface that decomposes as a result, exist the label information that calls the sequential requirement to judge according to a plurality of Open api interfaces of expression.
(1) if acquisition module 320 judge mark information is represented that a plurality of Open api interfaces do not exist and is called the sequential requirement as a result, acting server calls with the concurrent invocation pattern, by concurrent operations a plurality of Intranet HTTP requests is sent on the corresponding server of each Open api interface with wrapping data parallels.Initiate N Intranet HTTP request concurrently, after referring to send the Intranet HTTP request bag of an interface correspondence, begin to send the corresponding Intranet HTTP request of next interface bag immediately, asking bag all to send up to the Intranet HTTP of all N interface finishes, just begin to receive the return results of each interface, till the return results of all N interface all is received.
(2) if acquisition module 320 judge mark information are represented that a plurality of Open api interfaces exist and are called the sequential requirement as a result, then according to the arrangement of elements order of each Open api interface in the metamessage array, initiate the corresponding Intranet HTTP request of each Open api interface serially successively.Initiate N Intranet HTTP request serially, after referring to send the corresponding Intranet HTTP request of an interface bag, the return results of this interface is waited for and is received on block type ground synchronously, up to receiving return results, could continue to send next interface corresponding Intranet HTTP request bag and wait for its return results packet of reception, all finish up to the Intranet HTTP of all N interface request so repeatedly.
Gather and sending module 330 sends Intranet HTTP request bag data to the corresponding server of Open api interface, receive the result that this server returns, handle and be sent to third party's application end.
Behind the return results that receives the corresponding Intranet HTTP request of Open api interface, gather and sending module 330 with the return results of each api interface with default form, as forms such as JSON object or XML nodes, be described, and put it in JSON array or the XML object according to the order of each interface in the metamessage array, gather and sending module 330 is back to third party's application end with this JSON array or XML object.
Third party's application end is resolved return results according to each Open api interface putting in order in described metamessage array, with the corresponding return results of each Open api interface that obtains after receiving the return results of interface batch call request.
When needing to call the Open api interface of N no context data dependence relation in some service request processing procedures that the third party uses, application comprises the system of this acting server, and N Open api interface calls the time T 1 that consumes and can calculate by following formula:
Tie-time+N interface API of tie-time+N Intranet HTTP of 1 public network HTTP/HTTPS of T1 ≈ business is wrapped and transmission time+1 a public network HTTP/HTTPS request bag of respond packet and the transmission time of respond packet in processing time+N Intranet HTTP request of server end.
Adopt traditional implementation, consumption can be calculated by following formula this N the time T that the Open api interface calls 2:
Tie-time+N interface of N public network HTTP/HTTPS of T2 ≈ is asked the transmission time of bag and respond packet at processing time+N public network HTTP/HTTPS of service end.
Because the network speed of public network is low very more than inner-mesh network speed, each interface is compared also much smaller in the processing time of server end with the transmission time of data on public network simultaneously, therefore T2/T1 is close to N, be third party when being applied in the Open api interface that calls N no context data dependence relation, the performance of using native system will have nearly N lifting doubly.
Be example as Fig. 3 for three the Open api interfaces of A, B, C with third party's application call no context data dependence relation call, contrasted the sequential relationship of calling of using the native system front and back.As shown in Figure 3, a is for before using native system, and A, B, C interface are initiated request to server end successively, and accept the request of server end.B has to call the sequential relationship of using native system under the sequential situation, and A, B, three interfaces of C call in batches to acting server, and acting server initiates to ask and accept request to server according to sequential relationship successively.C does not call the sequential relationship of using native system under the sequential situation for having, and A, B, three interfaces of C call in batches to acting server, and acting server adopts the mode of concurrent invocation, initiates request to server simultaneously.Can draw the minimizing trend that obviously is total consuming time of a plurality of Open api interfaces of third party's application call among a, b, the c.
Acting server according to the embodiment of the invention is resolved and is called according to the batch call request, relatively flexibly, compare allocating time with classic method and reduce, can promote the performance that the third party uses, improved third party developer and used the user of the Open api interface of open platform to experience.
In the description of this instructions, concrete feature, structure, material or characteristics that the description of reference term " embodiment ", " some embodiment ", " example ", " concrete example " or " some examples " etc. means in conjunction with this embodiment or example description are contained at least one embodiment of the present invention or the example.In this manual, the schematic statement to above-mentioned term not necessarily refers to identical embodiment or example.And concrete feature, structure, material or the characteristics of description can be with the suitable manner combination in any one or more embodiment or example.
Although illustrated and described embodiments of the invention, for the ordinary skill in the art, be appreciated that without departing from the principles and spirit of the present invention and can carry out multiple variation, modification, replacement and modification to these embodiment that scope of the present invention is by claims and be equal to and limit.
Claims (28)
1. a batch calls the method for api interface, it is characterized in that, may further comprise the steps:
Third party's application end is obtained call address information and the call parameters information of a plurality of api interfaces, and to acting server transmission batch call request, wherein, described batch call request comprises the metamessage array that call address information and call parameters information by a plurality of api interfaces constitute;
Described acting server obtains corresponding a plurality of return results according to described metamessage array from described a plurality of api interfaces; And
Described acting server gathers described a plurality of return results and is sent to described third party's application end.
2. batch as claimed in claim 1 calls the method for api interface, it is characterized in that, also comprises:
The requirement that described third party's application end is called according to described batch is added in described batch call request and is called gomma.
3. batch as claimed in claim 2 calls the method for api interface, it is characterized in that, also comprises:
Described acting server obtains corresponding invocation pattern according to calling gomma, and obtains corresponding a plurality of return results according to invocation pattern and the described metamessage array of described correspondence from described a plurality of api interfaces.
4. batch as claimed in claim 3 calls the method for api interface, it is characterized in that,
Do not call gomma when described batch call request comprises, described acting server calls with the concurrent invocation pattern; And
Call gomma when described batch call request comprises, described acting server calls with the serial invocation pattern according to the order of described a plurality of api interfaces in described metamessage array.
5. call the method for api interface as each described batch of claim 1-4, it is characterized in that, also comprise:
Described acting server is a plurality of Intranet call address information with the call address information translation of described a plurality of api interfaces.
6. call the method for api interface as each described batch of claim 1-5, it is characterized in that, described acting server gathers described a plurality of return results and is sent to described third party's application end and further comprises:
Described acting server is described to generate a plurality of description results with the return results of described a plurality of api interfaces with default form.
7. batch as claimed in claim 6 calls the method for api interface, it is characterized in that, also comprises:
When comprising, described batch call request calls gomma, described acting server is put into described a plurality of description results to a JSON array or XML object according to the order of described a plurality of api interfaces in described metamessage array, and described JSON array or XML object are fed back to described third party's application end.
8. call the method for api interface as each described batch of claim 1-7, it is characterized in that, described call parameters information comprises parameter list that api interface imports into, calls the employed HTTP method of api interface.
9. a batch calls the system of api interface, it is characterized in that, comprises third party's application end, acting server and at least one API service end, wherein,
Described third party's application end, be used for obtaining call address information and the call parameters information of a plurality of api interfaces, and to described acting server transmission batch call request, wherein, described batch call request comprises the metamessage array that call address information and call parameters information by a plurality of api interfaces constitute;
Described acting server is used for obtaining corresponding a plurality of return results according to described metamessage array from described a plurality of api interfaces, and described a plurality of return results are gathered and are sent to described third party's application end; And
Described at least one API service end is used for providing described a plurality of api interface.
10. batch as claimed in claim 9 calls the system of api interface, it is characterized in that, described third party's application end, and the requirement that also is used for calling according to described batch is called gomma in described batch call request interpolation.
11. batch as claimed in claim 10 calls the system of api interface, it is characterized in that, described acting server, also be used for obtaining corresponding invocation pattern according to calling gomma, and obtain corresponding a plurality of return results according to invocation pattern and the described metamessage array of described correspondence from described a plurality of api interfaces.
12. batch as claimed in claim 11 calls the system of api interface, it is characterized in that, wherein,
Do not call gomma when described batch call request comprises, described acting server calls with the concurrent invocation pattern; And
Call gomma when described batch call request comprises, described acting server calls with the serial invocation pattern according to the order of described a plurality of api interfaces in described metamessage array.
13. call the system of api interface as each described batch of claim 9-12, it is characterized in that, described acting server, also the call address information translation that is used for described a plurality of api interfaces is a plurality of Intranet call address information.
14. call the system of api interface as each described batch of claim 9-12, it is characterized in that described acting server is described to generate a plurality of description results with the return results of described a plurality of api interfaces with default form.
15. batch as claimed in claim 14 calls the system of api interface, it is characterized in that, when comprising, described batch call request calls gomma, described acting server is put into described a plurality of description results to a JSON array or XML object according to the order of described a plurality of api interfaces in described metamessage array, and described JSON array or XML object are fed back to described third party's application end.
16. call the system of api interface as each described batch of claim 9-12, it is characterized in that described call parameters information comprises parameter list that api interface imports into, calls the employed HTTP method of api interface.
17. third party's application end is characterized in that, comprising:
Acquisition module is for call address information and the call parameters information of obtaining a plurality of api interfaces;
Sending module is used for sending call request in batches to acting server, and wherein, described batch call request comprises the metamessage array that is made of the call address information of a plurality of api interfaces and call parameters information; And
Receiver module be used for to receive the summarized results of a plurality of return results that described acting server obtains according to described metamessage array.
18. third party's application end as claimed in claim 17 is characterized in that, also comprises:
Add module, the requirement that is used for calling according to described batch is called gomma in described batch call request interpolation.
19. third party's application end as claimed in claim 18, it is characterized in that, described acting server obtains corresponding invocation pattern according to calling gomma, and obtains corresponding a plurality of return results according to invocation pattern and the described metamessage array of described correspondence from described a plurality of api interfaces.
20. third party's application end as claimed in claim 17 is characterized in that, described call parameters information comprises parameter list that api interface imports into, calls the employed HTTP method of api interface.
21. an acting server is characterized in that, comprising:
Receiver module is used for receiving the batch call request that third party's application end sends to acting server, and wherein, described batch call request comprises the metamessage array that is made of the call address information of a plurality of api interfaces and call parameters information;
Acquisition module is used for obtaining corresponding a plurality of return results according to described metamessage array from described a plurality of api interfaces as a result; And
Gather and sending module, be used for described a plurality of return results are gathered and are sent to described third party's application end.
22. acting server as claimed in claim 21 is characterized in that, wherein, has the gomma of calling in the described batch call request.
23. acting server as claimed in claim 22, it is characterized in that, described acquisition module as a result obtains corresponding invocation pattern according to calling gomma, and obtains corresponding a plurality of return results according to invocation pattern and the described metamessage array of described correspondence from described a plurality of api interfaces.
24. acting server as claimed in claim 23 is characterized in that,
Do not call gomma when described batch call request comprises, described acting server calls with the concurrent invocation pattern; And
Call gomma when described batch call request comprises, described acting server calls with the serial invocation pattern according to the order of described a plurality of api interfaces in described metamessage array.
25. as each described acting server of claim 21-24, it is characterized in that, also comprise:
Modular converter, the call address information translation that is used for described a plurality of api interfaces is a plurality of Intranet call address information.
26., it is characterized in that described gather and sending module is described to generate a plurality of description results with the return results of described a plurality of api interfaces with default form as each described acting server of claim 21-25.
27. acting server as claimed in claim 26, it is characterized in that, when comprising, described batch call request calls gomma, described gather and sending module is put into described a plurality of description results to a JSON array or XML object according to the order of described a plurality of api interfaces in described metamessage array, and described JSON array or XML object are fed back to described third party's application end.
28. acting server as claimed in claim 21 is characterized in that, described call parameters information comprises parameter list that api interface imports into, calls the employed HTTP method of api interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310217832.4A CN103345420B (en) | 2013-06-03 | 2013-06-03 | Batch calls the mthods, systems and devices of api interface |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310217832.4A CN103345420B (en) | 2013-06-03 | 2013-06-03 | Batch calls the mthods, systems and devices of api interface |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103345420A true CN103345420A (en) | 2013-10-09 |
| CN103345420B CN103345420B (en) | 2017-12-22 |
Family
ID=49280218
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310217832.4A Active CN103345420B (en) | 2013-06-03 | 2013-06-03 | Batch calls the mthods, systems and devices of api interface |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103345420B (en) |
Cited By (42)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103905551A (en) * | 2014-04-02 | 2014-07-02 | 北京中交兴路车联网科技有限公司 | Method and device for calling service |
| CN104580501A (en) * | 2015-01-23 | 2015-04-29 | 广东能龙教育股份有限公司 | Http interface dynamic publishing method and system based on reflex mechanism |
| CN104732331A (en) * | 2015-02-13 | 2015-06-24 | 腾讯科技（深圳）有限公司 | Grouping management method, device and system |
| CN104852939A (en) * | 2014-02-18 | 2015-08-19 | 中国电信股份有限公司 | Capability interface deploying method and system |
| CN105516215A (en) * | 2014-09-22 | 2016-04-20 | 阿里巴巴集团控股有限公司 | Asynchronous call method and asynchronous call device |
| CN106470226A (en) * | 2015-08-18 | 2017-03-01 | 阿里巴巴集团控股有限公司 | The Proxy Method of a kind of client and service end mutual message and device |
| CN106484603A (en) * | 2015-08-26 | 2017-03-08 | 阿里巴巴集团控股有限公司 | A kind of service test method and device |
| CN106557698A (en) * | 2016-11-29 | 2017-04-05 | 武汉斗鱼网络科技有限公司 | A kind of component detection method and apparatus in application |
| CN106648858A (en) * | 2016-11-29 | 2017-05-10 | 深圳市捷顺科技实业股份有限公司 | Interactive management system for C# interface data |
| CN106802859A (en) * | 2015-11-25 | 2017-06-06 | 北京京东尚科信息技术有限公司 | A kind of method and device of client software test |
| CN106959672A (en) * | 2017-04-28 | 2017-07-18 | 深圳市汇川控制技术有限公司 | A kind of industrial kinetic control system and method based on API |
| CN107046482A (en) * | 2017-04-25 | 2017-08-15 | 厦门集微科技有限公司 | The management method and device of a kind of API service |
| CN107231398A (en) * | 2016-03-25 | 2017-10-03 | 阿里巴巴集团控股有限公司 | Information interacting method and device |
| CN107423041A (en) * | 2016-03-31 | 2017-12-01 | 阿里巴巴集团控股有限公司 | Method and apparatus for realizing application programming interface configuration and calling |
| CN107623788A (en) * | 2017-09-22 | 2018-01-23 | 努比亚技术有限公司 | Using the raising method, apparatus and computer-readable recording medium of toggle speed |
| CN107678794A (en) * | 2017-09-22 | 2018-02-09 | 努比亚技术有限公司 | Application program launching interface merging method and mobile terminal |
| CN107733879A (en) * | 2017-09-29 | 2018-02-23 | 努比亚技术有限公司 | Client terminal start-up method, mobile terminal and computer storage media |
| CN107729215A (en) * | 2017-10-30 | 2018-02-23 | 努比亚技术有限公司 | Interface interchange method, mobile terminal and computer-readable recording medium |
| CN107748681A (en) * | 2017-10-27 | 2018-03-02 | 努比亚技术有限公司 | A kind of interface merges control method, equipment and computer-readable recording medium |
| CN107809332A (en) * | 2017-11-10 | 2018-03-16 | 中国民生银行股份有限公司 | Compound interface configures and compound interface call method, device |
| CN107818022A (en) * | 2017-10-25 | 2018-03-20 | 努比亚技术有限公司 | Application programming interfaces merging method, mobile terminal and computer-readable recording medium |
| CN107832163A (en) * | 2017-11-29 | 2018-03-23 | 努比亚技术有限公司 | A kind of buffering updating method, server and computer-readable recording medium |
| CN107888631A (en) * | 2016-09-28 | 2018-04-06 | 北京京东尚科信息技术有限公司 | A kind of interface interchange method and apparatus of configurable combination |
| CN107920094A (en) * | 2016-10-08 | 2018-04-17 | 阿里巴巴集团控股有限公司 | Data capture method, device, server and the network equipment |
| CN107918562A (en) * | 2016-10-11 | 2018-04-17 | 北京京东尚科信息技术有限公司 | A kind of unified interface management method and system |
| CN108279985A (en) * | 2017-12-22 | 2018-07-13 | 努比亚技术有限公司 | A kind of interface requests agreement remodeling method, equipment and computer readable storage medium |
| CN108696568A (en) * | 2018-02-23 | 2018-10-23 | 福建天泉教育科技有限公司 | A kind of request batch processing method and terminal |
| CN109165935A (en) * | 2018-07-02 | 2019-01-08 | 平安科技（深圳）有限公司 | Batch payment method, device, computer equipment and storage medium |
| CN109218371A (en) * | 2017-07-06 | 2019-01-15 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus calling data |
| CN109901989A (en) * | 2017-12-11 | 2019-06-18 | 优酷网络技术（北京）有限公司 | JSON control methods and device and electronic equipment |
| CN110134429A (en) * | 2019-04-02 | 2019-08-16 | 惠州学院 | Network information browsing method, device, equipment, storage medium and system |
| US10437634B1 (en) | 2018-04-16 | 2019-10-08 | Microsoft Technology Licensing Llc | Independently threading API calls to service a request |
| CN110502319A (en) * | 2019-08-23 | 2019-11-26 | 腾讯科技（深圳）有限公司 | Processing method, device, electronic equipment and the storage medium of distributed transaction |
| CN110837446A (en) * | 2018-08-16 | 2020-02-25 | 北京嘉楠捷思信息技术有限公司 | Equipment management method and device applied to embedded system, medium and embedded equipment |
| CN110838957A (en) * | 2019-11-27 | 2020-02-25 | 深圳开思时代科技有限公司 | API interface debugging method based on server |
| CN111142960A (en) * | 2018-11-02 | 2020-05-12 | 中国电信股份有限公司 | Interface providing method, device and system |
| CN111552578A (en) * | 2020-04-30 | 2020-08-18 | 成都新潮传媒集团有限公司 | Third-party interface calling method and device |
| CN112732417A (en) * | 2019-10-28 | 2021-04-30 | 北京京东振世信息技术有限公司 | Method and device for processing application request |
| CN112882852A (en) * | 2021-03-25 | 2021-06-01 | 上海科世达-华阳汽车电器有限公司 | Interface data storage method and device and computer readable storage medium |
| CN115174683A (en) * | 2022-06-29 | 2022-10-11 | 广州鲁邦通智能科技有限公司 | Request method and system for calling query interface |
| WO2023024035A1 (en) * | 2021-08-26 | 2023-03-02 | 阿波罗智联(北京)科技有限公司 | Request processing method and apparatus, electronic device, and storage medium |
| TWI828167B (en) * | 2022-04-18 | 2024-01-01 | 大陸商鼎捷軟件股份有限公司 | Automated service arrangement and execution system and method thereof |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1867898A (en) * | 2003-10-14 | 2006-11-22 | 国际商业机器公司 | Method and apparatus for processing service requests in a service-oriented architecture |
| CN102521408A (en) * | 2011-12-27 | 2012-06-27 | 北京人大金仓信息技术股份有限公司 | Method for accessing flat file by using java database connectivity (JDBC) interface |
| CN102880475A (en) * | 2012-10-23 | 2013-01-16 | 上海普元信息技术股份有限公司 | Real-time event handling system and method based on cloud computing in computer software system |
| CN102957696A (en) * | 2012-10-25 | 2013-03-06 | 北京奇虎科技有限公司 | Data processing method and device |
-
2013
- 2013-06-03 CN CN201310217832.4A patent/CN103345420B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1867898A (en) * | 2003-10-14 | 2006-11-22 | 国际商业机器公司 | Method and apparatus for processing service requests in a service-oriented architecture |
| CN102521408A (en) * | 2011-12-27 | 2012-06-27 | 北京人大金仓信息技术股份有限公司 | Method for accessing flat file by using java database connectivity (JDBC) interface |
| CN102880475A (en) * | 2012-10-23 | 2013-01-16 | 上海普元信息技术股份有限公司 | Real-time event handling system and method based on cloud computing in computer software system |
| CN102957696A (en) * | 2012-10-25 | 2013-03-06 | 北京奇虎科技有限公司 | Data processing method and device |
Cited By (59)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104852939A (en) * | 2014-02-18 | 2015-08-19 | 中国电信股份有限公司 | Capability interface deploying method and system |
| CN104852939B (en) * | 2014-02-18 | 2018-07-24 | 中国电信股份有限公司 | A kind of method and system of deployment ability interface |
| CN103905551A (en) * | 2014-04-02 | 2014-07-02 | 北京中交兴路车联网科技有限公司 | Method and device for calling service |
| CN103905551B (en) * | 2014-04-02 | 2018-07-24 | 北京中交兴路车联网科技有限公司 | A kind of service calling method and device |
| CN105516215A (en) * | 2014-09-22 | 2016-04-20 | 阿里巴巴集团控股有限公司 | Asynchronous call method and asynchronous call device |
| CN105516215B (en) * | 2014-09-22 | 2018-11-16 | 阿里巴巴集团控股有限公司 | Asynchronous invoking method and device |
| CN104580501A (en) * | 2015-01-23 | 2015-04-29 | 广东能龙教育股份有限公司 | Http interface dynamic publishing method and system based on reflex mechanism |
| CN104732331A (en) * | 2015-02-13 | 2015-06-24 | 腾讯科技（深圳）有限公司 | Grouping management method, device and system |
| US10637676B2 (en) | 2015-02-13 | 2020-04-28 | Tencent Technology (Shenzhen) Company Limited | Method, apparatus, and system for managing follower accounts in groups |
| CN106470226A (en) * | 2015-08-18 | 2017-03-01 | 阿里巴巴集团控股有限公司 | The Proxy Method of a kind of client and service end mutual message and device |
| CN106484603B (en) * | 2015-08-26 | 2019-08-09 | 阿里巴巴集团控股有限公司 | A kind of service test method and device |
| CN106484603A (en) * | 2015-08-26 | 2017-03-08 | 阿里巴巴集团控股有限公司 | A kind of service test method and device |
| CN106802859A (en) * | 2015-11-25 | 2017-06-06 | 北京京东尚科信息技术有限公司 | A kind of method and device of client software test |
| CN107231398A (en) * | 2016-03-25 | 2017-10-03 | 阿里巴巴集团控股有限公司 | Information interacting method and device |
| CN107423041A (en) * | 2016-03-31 | 2017-12-01 | 阿里巴巴集团控股有限公司 | Method and apparatus for realizing application programming interface configuration and calling |
| CN107423041B (en) * | 2016-03-31 | 2021-05-07 | 阿里巴巴集团控股有限公司 | Method and apparatus for implementing application programming interface configuration and invocation |
| CN107888631A (en) * | 2016-09-28 | 2018-04-06 | 北京京东尚科信息技术有限公司 | A kind of interface interchange method and apparatus of configurable combination |
| CN107920094B (en) * | 2016-10-08 | 2021-07-16 | 阿里巴巴集团控股有限公司 | Data acquisition method and device, server and network equipment |
| CN107920094A (en) * | 2016-10-08 | 2018-04-17 | 阿里巴巴集团控股有限公司 | Data capture method, device, server and the network equipment |
| CN107918562A (en) * | 2016-10-11 | 2018-04-17 | 北京京东尚科信息技术有限公司 | A kind of unified interface management method and system |
| CN106557698A (en) * | 2016-11-29 | 2017-04-05 | 武汉斗鱼网络科技有限公司 | A kind of component detection method and apparatus in application |
| CN106557698B (en) * | 2016-11-29 | 2019-08-02 | 武汉斗鱼网络科技有限公司 | A kind of component detection method and apparatus in application |
| CN106648858A (en) * | 2016-11-29 | 2017-05-10 | 深圳市捷顺科技实业股份有限公司 | Interactive management system for C# interface data |
| CN107046482A (en) * | 2017-04-25 | 2017-08-15 | 厦门集微科技有限公司 | The management method and device of a kind of API service |
| CN107046482B (en) * | 2017-04-25 | 2019-10-11 | 厦门集微科技有限公司 | A kind of management method and device of API service |
| CN106959672B (en) * | 2017-04-28 | 2020-07-28 | 深圳市汇川控制技术有限公司 | Industrial motion control system and method based on API |
| CN106959672A (en) * | 2017-04-28 | 2017-07-18 | 深圳市汇川控制技术有限公司 | A kind of industrial kinetic control system and method based on API |
| CN109218371A (en) * | 2017-07-06 | 2019-01-15 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus calling data |
| CN107623788A (en) * | 2017-09-22 | 2018-01-23 | 努比亚技术有限公司 | Using the raising method, apparatus and computer-readable recording medium of toggle speed |
| CN107678794B (en) * | 2017-09-22 | 2021-01-01 | 努比亚技术有限公司 | Application program starting interface merging method and mobile terminal |
| CN107678794A (en) * | 2017-09-22 | 2018-02-09 | 努比亚技术有限公司 | Application program launching interface merging method and mobile terminal |
| CN107733879A (en) * | 2017-09-29 | 2018-02-23 | 努比亚技术有限公司 | Client terminal start-up method, mobile terminal and computer storage media |
| CN107818022B (en) * | 2017-10-25 | 2021-08-24 | 努比亚技术有限公司 | Application program interface merging method, mobile terminal and computer readable storage medium |
| CN107818022A (en) * | 2017-10-25 | 2018-03-20 | 努比亚技术有限公司 | Application programming interfaces merging method, mobile terminal and computer-readable recording medium |
| CN107748681A (en) * | 2017-10-27 | 2018-03-02 | 努比亚技术有限公司 | A kind of interface merges control method, equipment and computer-readable recording medium |
| CN107729215A (en) * | 2017-10-30 | 2018-02-23 | 努比亚技术有限公司 | Interface interchange method, mobile terminal and computer-readable recording medium |
| CN107809332A (en) * | 2017-11-10 | 2018-03-16 | 中国民生银行股份有限公司 | Compound interface configures and compound interface call method, device |
| CN107832163A (en) * | 2017-11-29 | 2018-03-23 | 努比亚技术有限公司 | A kind of buffering updating method, server and computer-readable recording medium |
| CN109901989A (en) * | 2017-12-11 | 2019-06-18 | 优酷网络技术（北京）有限公司 | JSON control methods and device and electronic equipment |
| CN109901989B (en) * | 2017-12-11 | 2023-12-12 | 阿里巴巴（中国）有限公司 | JSON comparison method and device and electronic equipment |
| CN108279985B (en) * | 2017-12-22 | 2021-11-19 | 努比亚技术有限公司 | Interface request protocol transformation method, equipment and computer readable storage medium |
| CN108279985A (en) * | 2017-12-22 | 2018-07-13 | 努比亚技术有限公司 | A kind of interface requests agreement remodeling method, equipment and computer readable storage medium |
| CN108696568A (en) * | 2018-02-23 | 2018-10-23 | 福建天泉教育科技有限公司 | A kind of request batch processing method and terminal |
| CN108696568B (en) * | 2018-02-23 | 2021-07-06 | 福建天泉教育科技有限公司 | Request batch processing method and terminal |
| US10437634B1 (en) | 2018-04-16 | 2019-10-08 | Microsoft Technology Licensing Llc | Independently threading API calls to service a request |
| CN109165935A (en) * | 2018-07-02 | 2019-01-08 | 平安科技（深圳）有限公司 | Batch payment method, device, computer equipment and storage medium |
| CN110837446A (en) * | 2018-08-16 | 2020-02-25 | 北京嘉楠捷思信息技术有限公司 | Equipment management method and device applied to embedded system, medium and embedded equipment |
| CN111142960B (en) * | 2018-11-02 | 2023-11-14 | 中国电信股份有限公司 | Interface providing method, device and system |
| CN111142960A (en) * | 2018-11-02 | 2020-05-12 | 中国电信股份有限公司 | Interface providing method, device and system |
| CN110134429A (en) * | 2019-04-02 | 2019-08-16 | 惠州学院 | Network information browsing method, device, equipment, storage medium and system |
| CN110502319A (en) * | 2019-08-23 | 2019-11-26 | 腾讯科技（深圳）有限公司 | Processing method, device, electronic equipment and the storage medium of distributed transaction |
| CN112732417A (en) * | 2019-10-28 | 2021-04-30 | 北京京东振世信息技术有限公司 | Method and device for processing application request |
| CN110838957A (en) * | 2019-11-27 | 2020-02-25 | 深圳开思时代科技有限公司 | API interface debugging method based on server |
| CN111552578A (en) * | 2020-04-30 | 2020-08-18 | 成都新潮传媒集团有限公司 | Third-party interface calling method and device |
| CN112882852A (en) * | 2021-03-25 | 2021-06-01 | 上海科世达-华阳汽车电器有限公司 | Interface data storage method and device and computer readable storage medium |
| WO2023024035A1 (en) * | 2021-08-26 | 2023-03-02 | 阿波罗智联(北京)科技有限公司 | Request processing method and apparatus, electronic device, and storage medium |
| TWI828167B (en) * | 2022-04-18 | 2024-01-01 | 大陸商鼎捷軟件股份有限公司 | Automated service arrangement and execution system and method thereof |
| CN115174683B (en) * | 2022-06-29 | 2023-10-13 | 广州鲁邦通智能科技有限公司 | Request method and system for calling query interface |
| CN115174683A (en) * | 2022-06-29 | 2022-10-11 | 广州鲁邦通智能科技有限公司 | Request method and system for calling query interface |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103345420B (en) | 2017-12-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103345420A (en) | Method for massively calling API interfaces, system for massively calling API interfaces and device for massively calling API interfaces | |
| US10135923B2 (en) | Data transfer method and system | |
| CN111092877B (en) | Data processing method and device, electronic equipment and storage medium | |
| WO2016184175A1 (en) | Database processing method and apparatus | |
| CN110134534B (en) | System and method for optimizing message processing for big data distributed system based on NIO | |
| US20140162680A1 (en) | Providing Multiple Interfaces for Traffic | |
| CN107426233A (en) | Data communication system, method, Web server and monitoring system based on B/S frameworks | |
| CN101115050A (en) | Network service request processing system and method | |
| CN106230977B (en) | A kind of client functionality loading method, system, client and server-side | |
| CN111064771A (en) | Network request processing method and system | |
| AU2019256257A1 (en) | Processor core scheduling method and apparatus, terminal, and storage medium | |
| CN104468830A (en) | Web service method based on internet of things and internet of things system | |
| CN111200606A (en) | Deep learning model task processing method, system, server and storage medium | |
| CN110213155B (en) | Communication processing method, communication processing device, related equipment and storage medium | |
| CN110673970B (en) | Cross-process calling system and method based on web application | |
| CN106453494A (en) | Plug-in updating method, plug-in updating system, client and server side | |
| US20160150006A1 (en) | Device data transfer via a wireless interface | |
| CN116389454A (en) | Data downloading system | |
| CN113225830B (en) | Data network uplink scheduling method and device and electronic equipment | |
| CN107404504B (en) | Communication method, device and system | |
| CN114050909A (en) | Method and system for drilling simulated mails and electronic equipment | |
| CN102843424B (en) | A kind of heterogeneous distributed cloud computing system and method | |
| CN101909283B (en) | M2M (Machine-to-Machine) platform and method for sharing load downloaded with in high capacity | |
| CN106357798A (en) | Method for storing and acquiring media files in Portal page, cloud controller and terminal | |
| CN113098960A (en) | Service operation method, device, server and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |