CN109218297B - Method and device for requesting data - Google Patents
Method and device for requesting data Download PDFInfo
- Publication number
- CN109218297B CN109218297B CN201811019472.6A CN201811019472A CN109218297B CN 109218297 B CN109218297 B CN 109218297B CN 201811019472 A CN201811019472 A CN 201811019472A CN 109218297 B CN109218297 B CN 109218297B
- Authority
- CN
- China
- Prior art keywords
- access request
- api access
- request
- data
- fetch
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention relates to a method and a device for requesting data, wherein in the method, an Application Program Interface (API) access request for requesting data from a service server is determined; receiving response data returned by the AMP, wherein the response data is determined by the AMP according to an interface state of a data interface requested by the API access request, and when the interface state is in a development completion state, the response data is a response identifier used for indicating to send the API access request to the service server; and when the response identifier is determined to be received, sending the API access request to the service server, and requesting to acquire the data requested by the API access request. By the invention, all information interacted between the API access request and the service server can be maintained.
Description
Technical Field
The invention relates to the technical field of internet, in particular to a method and a device for requesting data.
Background
With the gradual maturity of World Wide Web (Web) development, the Web page architecture design with separated front and back ends is more and more approved by developers.
In the design of a Web page architecture with separated front and back ends, the front end can be understood as a Web page which runs on a terminal browser and is displayed for a user to browse, and can be used for friendly display, interactive experience, terminal compatibility and the like, and the back end is mainly used for interacting with a database to process corresponding business logic and is emphatically used for data processing, performance, safety and the like. When the front end has data demand, the back end can request to obtain the demanded data.
Currently, when there is a data demand, a front end sends an Application Programming Interface (API) access request (for example, a hypertext transfer protocol (HTTP) request) to an AMP, and the AMP returns different data according to a development state of an Interface for providing data at a back end. And in the state that the development of the back-end interface is not completed, the AMP provides analog (mock) data for the front end, in the state that the development of the back-end interface is completed, the AMP is used as an agent to proxy the API access request to the service server, and the service server provides real data for the front end.
However, in the process of acting the API access request to the service server by the AMP as a proxy, a cross-domain situation may occur because the domain name of the AMP and the domain name of the service server are not consistent. Under the condition of cross-domain, the security mechanism of some specific types of browsers determines that permission information cannot be carried during cross-domain access, and if the API access request sent by the front end to the AMP carries permission information for different role verifications, the permission information in the API access request cannot be sent to the service server, so that the service server cannot return real data requested by the API access request according to role permissions.
Disclosure of Invention
The embodiment of the invention provides a method and a device for requesting data, which are used for realizing that when a service server requests to acquire data requested by an API access request, the service server can return real data requested by the API access request according to role authority.
One aspect of the invention provides a method of requesting data, the method comprising determining an application program interface, API, access request for requesting data from a service server; receiving response data returned by the AMP, wherein the response data is determined by the AMP according to an interface state of a data interface requested by the API access request, and when the interface state is in a development completion state, the response data is a response identifier used for indicating to send the API access request to the service server; and when the response identifier is determined to be received, sending the API access request to the service server, and requesting to acquire the data requested by the API access request. .
Another aspect of the present invention also provides a method of requesting data, the method including determining an interface state of a data interface requested by an application program interface API access request; determining response data according to the interface state, wherein the response data is a response identifier for indicating to send the API access request to the service server when the interface state is in a development completion state; and returning the response data.
Yet another aspect of the present invention provides an apparatus for requesting data, which includes a determining unit, a receiving unit, and a requesting unit. The system comprises a determining unit, a processing unit and a processing unit, wherein the determining unit is used for determining an Application Program Interface (API) access request for requesting data to a service server; a receiving unit, configured to receive response data returned by an AMP, where the response data is determined by the AMP according to an interface state of a data interface requested by the API access request, and when the interface state is in a development completion state, the response data is a response identifier used to indicate that the API access request is sent to the service server; and the request unit is used for sending the API access request to the service server and requesting to acquire the data requested by the API access request when the response identifier is determined to be received. .
Still another aspect of the present invention also provides an apparatus for requesting data, which includes a determining unit and a transmitting unit. The determining unit is used for determining the interface state of a data interface requested by an application program interface API access request, and determining response data according to the interface state, wherein the response data is a response identifier used for indicating to send the API access request to the service server when the interface state is in a development completion state; and the sending unit is used for returning the response data.
The method and the device for requesting data provided by the invention receive response data returned by the AMP, when the interface state is in a development completion state, the response data is a response identifier used for indicating to send the API access request to the service server, when the response identifier used for indicating to send the API access request to the service server is determined to be received, the API access request is sent to the service server, and the data requested by the API access request is requested to be obtained, the API access request is not required to be forwarded by the AMP, the API access request is not required to be changed, and all information (including authority information related to authentication) interacted between the API access request and the service server is maintained by adopting a mode of delaying sending the API access request.
Drawings
FIG. 1 is a flow chart illustrating a method for requesting data according to an embodiment of the present invention;
FIG. 2 is a flow chart illustrating another method for requesting data according to an embodiment of the present invention;
FIG. 3 is a flow chart illustrating another method for requesting data according to an embodiment of the present invention;
FIG. 4 is a flowchart illustrating another method for requesting data according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of an apparatus for requesting data according to an embodiment of the present invention;
fig. 6 is a schematic diagram illustrating a configuration of another apparatus for requesting data according to an embodiment of the present invention.
Detailed Description
The principles and spirit of the present invention will be described with reference to a number of exemplary embodiments. It is understood that these embodiments are given solely for the purpose of enabling those skilled in the art to better understand and to practice the invention, and are not intended to limit the scope of the invention in any way.
The method and the device for requesting data provided by the embodiment of the invention can be applied to an application scene that a front end requests to acquire back end data in a Web webpage framework with separated front and back ends. In the embodiment of the invention, the API access request is determined, the response data returned by the AMP is received, when the interface state is in a development completion state, the response data is a response identifier used for indicating the transmission of the API access request to the service server, when the response identifier used for indicating the transmission of the API access request to the service server is determined to be received, the API access request is transmitted to the service server, the data requested by the API access request is requested to be obtained, the API access request does not need to be forwarded through the AMP, and further, the interaction of all information (including authority information related to authentication) between the API access request and the service server can be maintained.
Fig. 1 is a flowchart illustrating an implementation of a method 100 for requesting data according to an embodiment of the present invention, where the method 100 may be executed by a main body that sends an API access request from a front end, where the main body may be a browser or other execution main bodies that can implement corresponding functions, and the embodiment of the present invention is not limited herein. For convenience of description, the execution subject executing the method 100 is referred to as an API proxy. Referring to fig. 1, the method 100 for requesting data includes:
s101: the API proxy determines an API access request for requesting data from the service server.
The API access request in the embodiment of the present invention may be sent when the front end has a data requirement. For example, the API access request may be a service request initiated by a client when there is a service requirement. The API access request typically includes a parameter that is unique for identifying the interface providing the data, for example, the API access request may be a domain name + request method (e.g., GET, POST, etc.) + path (e.g., https:// service.com/user), and the parameter for identifying the interface providing the data may be a user in https:// service.com/user).
In a possible implementation manner, the API access request in the embodiment of the present invention may be an HTTP request, an HTTP (Hyper Text Transfer Protocol over Secure Socket L eye, HTTPs) request based on a Secure Socket L eye, SS L.
S102: the API proxy receives response data returned by the AMP.
In this embodiment of the present invention, the AMP may determine the interface status of the data interface requested by the API access request, and generally, the determination of the interface status is performed after receiving a request for querying the interface status. The interface state may include an in-development state and a development-completed state.
In this embodiment of the present invention, the response data returned by the AMP may be understood as response data returned by the AMP when the AMP queries the interface status after receiving the request for querying the interface status, where the response data is determined by the AMP according to the interface status of the data interface requested by the API access request. The interface state may include an in-development state and a development-completed state.
And when the interface state is in a development completion state, the response data is a response identifier for indicating that an API access request is sent to the service server.
In another possible implementation, the response data is analog data fed back by the AMP when the interface state is in the development state.
S103: and when the response identifier is determined to be received, sending an API access request to the service server, and requesting to acquire the data requested by the API access request.
According to the method for requesting data provided by the embodiment of the invention, the API access request is not required to be changed, and all information (including authority information related to authentication) between the API access request and the service server is maintained by adopting a mode of delaying the transmission of the API access request.
The following describes an implementation method of request data according to an embodiment of the present invention with reference to practical applications.
In a possible implementation manner, in the method for requesting data provided by the embodiment of the present invention, an AMP request is generated according to an API access request sent by a front end, and the generated AMP request is sent to an AMP, where the AMP request includes an interface state query parameter, so that the AMP queries an interface state according to the AMP request, and returns a response identifier for indicating sending of the API access request to a service server when the interface state is in a development completion state, and then the data requested by the API access request can be requested from the service server according to the response identifier, and sending of the API access request by the AMP is not needed, and further the permission information in the API access request can be sent to the service server, so that the service server can return real data requested by the API access request according to role permissions.
Fig. 2 is a flowchart illustrating an implementation of a method 200 for requesting data according to an embodiment of the present invention, and referring to fig. 2, the method 200 includes:
s201: the API proxy determines an API access request for requesting data from the service server.
S202: the API proxy generates an AMP request from the API access request.
The AMP request referred to in the embodiments of the present invention is an AMP request that can be understood as a request for suspending sending of the API access request and for requesting the AMP to query the interface status of the data interface requested by the API access request.
In a possible implementation manner, an embodiment of the present invention may analyze a parameter in the API access request, and generate an AMP request, where the generated AMP request includes an interface state query parameter, and the interface state query parameter is used for the AMP to query an interface, where the service server provides data requested by the API access request, and query an interface state of the interface. For example, the interface status query parameters may include definitions, attributes, etc. of the interface.
S203: the API proxy sends the generated AMP request to the AMP.
S204: and the AMP acquires the AMP request sent by the API agent, analyzes the acquired AMP request and determines the interface state of the data interface requested by the API access request according to the AMP request.
Wherein, the AMP can inquire the interface state of the data interface requested by the API access request according to the interface state inquiry parameter in the AMP request.
In the embodiment of the invention, the AMP can inquire whether the interface state of the data interface requested by the API access request is in a development state or in a development completion state according to the interface state inquiry parameter in the AMP request.
S205: and the AMP determines and transmits response data according to the inquired interface state. And the API agent receives the response data sent by the AMP and acquires the data requested by the API access request according to the response data request.
In the embodiment of the present invention, the AMP may transmit different response data according to whether the interface state is in the development state or in the development completion state. In one possible implementation, if the AMP determines that the interface status is in the development status, the response data sent by the AMP may be mock data. Wherein the mock data may be analog data generated by the AMP according to an interface definition, the interface definition being an interface definition of an interface providing data requested by the API access request. In another possible implementation manner, if the AMP determines that the interface state is in the development complete state, the response data sent by the AMP may be a response identifier for indicating that the API access request is sent to the service server. In a possible example, the response identification may be a special response code, e.g., { code:' 200302 }.
If the response data is mock data, the API agent can feed back the received mock data to the client as the data requested by the API access request. If the response data is the response identification, the API access request can be sent to the service server according to the response identification, and the data requested by the API access request is requested. And after the data requested by the API access request is acquired from the service server, the data is fed back to the client.
According to the method for requesting data, the API agent acquires the API access request, generates the AMP request according to the API access request, and sends the generated AMP request to the AMP, wherein the AMP request comprises the interface state query parameter, so that the AMP can query the interface state according to the AMP request. And when the interface state is in a development completion state, the AMP returns a response identifier for indicating that the API access request is sent to the service server, and then the API agent can request the data requested by the API access request from the service server according to the response identifier without sending the API access request through the AMP.
The embodiment of the present invention will be described below by way of example with reference to the application of the above-mentioned request data.
The embodiment of the invention is described by taking an API access request as an HTTP request of a browser environment as an example, the HTTP request of the browser environment is generally determined by XM L HTTP request or by Fetch.
In a possible implementation manner, when the API access request is determined by XM L http request, an implementation flow of generating an AMP request according to the API access request according to the embodiment of the present invention may include:
s2021a, creating XM L HttpRequest with the same name as XM L HttpRequest to obtain a new XM L HttpRequest, wherein the attributes and the method defined in the new XM L HttpRequest are the same as those of the XM L HttpRequest.
For convenience in description in the embodiment of the present invention, XM L HttpRequest used when generating the API access request is referred to as native XM L HttpRequest.
The XM L HttpRequest created in the embodiment of the invention comprises the attributes and methods with the same name as the native XM L HttpRequest, for example, the sending (send) method with the same name and the opening (open) method with the same name.
S2022a renaming the native XM L HttpRequest to obtain the renamed XM L HttpRequest.
S2023a, analyzing the API access request in an open method in the newly-created XM L HttpRequest to obtain an interface state query parameter, wherein the interface state query parameter is used for the AMP query service server to provide the interface state of the data interface requested by the API access request.
S2024a, temporarily storing the data required to be sent by the API access request in the send method of the newly-created XM L HttpRequest.
In the embodiment of the invention, for example, the data required to be sent by the API access request can be saved in a table with a request Uniform Resource locator (Uniform Resource L atom, UR L) as an index), the sending of the API access request is suspended (because the API access request is really initiated only when the send method of XM L HttpRequest is called, only the cached data does not call the send method of the API access request.)
S2025a, combining the renamed XM L HttpRequest with the interface state query parameter to obtain the AMP request.
When the API access request is an XM L http request access request, an implementation process of requesting, by an API proxy in S205, to acquire data requested by the API access request may include:
calling data required to be sent by the API access request temporarily stored in the send method of the newly-built XM L HttpRequest, and requesting the service server to acquire the data required to be sent by the API access request temporarily stored in the send method by using the renamed XM L HttpRequest.
Fig. 3 is a flowchart illustrating an implementation of a method 300 for requesting data according to an embodiment of the present invention when an API access request is determined by XM L http request.
In the embodiment of the invention, an API access request (HTTP request) is analyzed in an open method of an XM L HttpRequest to obtain an interface state query parameter (such as a domain name + request method + path) for querying an interface state in the AMP, then the saved renamed XM L HttpRequest is called, the interface state query parameter is carried in the renamed XM L HttpRequest, and the interface state query parameter is sent to the AMP.
In another possible implementation manner, the API access request according to the embodiment of the present invention is determined by Fetch. When the API access request is determined by Fetch, an implementation flow for generating an AMP request according to the API access request may include:
s2021 b: and newly creating a Fetch with the same name as the Fetch to obtain the newly created Fetch, and defining the attribute and the method with the same name as the Fetch used for determining the API access request in the newly created Fetch.
S2022b renaming Fetch used in determining the API access request, obtaining the renamed Fetch.
S2023b, encapsulating the premium entrance outside the newly-built Fetch, and suspending the sending of the API access request by using a premium asynchronous processing mechanism.
S2024b, analyzing the newly-built Fetch to obtain data required to be sent by the API access request and interface state query parameters, wherein the interface state query parameters are used for the AMP query service server to provide the interface state of the data interface required by the API access request.
S2025b, combining the rename Fetch and the interface state query parameter to obtain the AMP request.
When the API access request is determined by the Fetch, the implementation process of requesting to acquire the data requested by the API access request in the embodiment of the present invention may include: and calling the renamed Fetch and suspending the sent API access request, and sending the API access request to the service server.
Fig. 4 is a flowchart illustrating an implementation of a method 400 for requesting data according to an embodiment of the present invention when an API access request is determined by Fetch.
In the embodiment of the invention, when the API access request is determined by the Fetch, the internal method of the Fetch cannot be read from the outside, but because the Fetch is implemented based on the Promise (a new asynchronous processing mechanism), the deferred sending of the API access request can be implemented by using the Promise property (waiting (wait) key before asynchronous operation can wait for the completion of the asynchronous operation and block the continuous execution of the current thread).
In a possible implementation manner, in the embodiment of the present invention, a function of sending the API access request to the service server when determining that the response identifier is received is encapsulated in the data request control, and the data request control is embedded in the front-end page, so as to implement flexible selection of whether to use the method for requesting data provided by the embodiment of the present invention by turning on and off the data request control.
In a possible implementation manner, the data request control may be a pluggable control, and the pluggable control may implement the on and off of the implementation function of delaying sending the API access request in the embodiment of the present invention. When the implementation function for delaying the API access request provided by the embodiment of the invention is required to be used for requesting data, the pluggable control can be inserted into the front-end page, and when the implementation function for delaying the API access request provided by the embodiment of the invention is not required to be used for requesting data, the pluggable control can be pulled out. This implementation is flexible.
Specifically, in the embodiment of the present invention, a configurable plug-in, such as a web-over-hypertext markup language web-packaging plug-in (Html Webpack plug-in) of web-packaging (Webpack), may be customized by using a packaging tool, and a new plug-in is defined by using a hook event of the configurable plug-in and is referred to in a packaging configuration, where the plug-in opens a function of controlling whether to start to defer sending of an API access request. If the plug-in is started, the plug-in is automatically inserted into a front-end page in a development environment, so that the function of delaying the transmission of the API access request is started, and the business code can not be invaded. Of course, the specific implementation manners of implementing pluggable (i.e., on/off) in the embodiment of the present invention are many, and the mainstream packaging tools (e.g., webpack, rollup, etc.) have similar functions, or similar functions can be implemented by writing scripts.
Based on the same inventive concept, the embodiment of the invention also provides a device for requesting data, and the device for requesting data can be applied to the API agent.
As shown in fig. 5, an embodiment of the present invention provides an apparatus 500 for requesting data, and the apparatus 500 for requesting data may be applied to an API proxy. The apparatus 500 for requesting data applied to the API proxy includes a determining unit 501, a receiving unit 502, and a requesting unit 503. The determining unit 501 is configured to determine an API access request for requesting data from a service server. A receiving unit 502, configured to receive response data returned by the AMP, where the response data is determined by the AMP according to an interface state of a data interface requested by the API access request, and when the interface state is in a development complete state, the response data is a response identifier used for indicating that the API access request is sent to the service server. A requesting unit 503, configured to send the API access request to the service server when determining that the response identifier is received, and request to acquire data requested by the API access request.
In a possible implementation, the apparatus 500 for requesting data further includes a generating unit 504 and a sending unit 505.
The generating unit 504 is configured to generate an AMP request according to the API access request before the receiving unit 502 receives response data returned by the AMP, where the AMP request is used to request to suspend sending of the API access request, and is used to request the AMP to query an interface state of a data interface requested by the API access request. The sending unit 505 is configured to send the AMP request generated by the generating unit 504 to an AMP.
In a possible example, the interface state is an in-development state, and the response data is analog data fed back by the AMP.
In one possible embodiment, when the API access request is determined by XM L http request, the generating unit 504 generates an AMP request according to the API access request in the following manner:
the method comprises the steps of creating an XM L HttpRequest which has the same name as the XM L HttpRequest to obtain a new XM L HttpRequest, defining an attribute and a method which have the same name as the XM L HttpRequest in the new XM L HttpRequest, analyzing an API access request in an open method in the new XM L HttpRequest to obtain an interface state query parameter, wherein the interface state query parameter is used for providing an interface state of a data interface requested by the API access request by an AMP inquiry service server, temporarily storing data required to be sent by the API access request in a presented method of the new XM L HttpRequest, renaming the XM L HttpRequest to obtain a rename XM L HttpRequest, combining the rename XM L Httequest with the interface state query parameter to obtain the AMP request, sending the API access request to the API access request by the XM L HttpRequest, and sending the API access request to the API request by the API access server in the following mode:
calling the data required by the API access request temporarily stored in the send method of the newly-built XM L HttpRequest, and requesting the data required by the API access request from the service server by using the renamed XM L HttpRequest.
In another possible embodiment, the API access request is determined by Fetch, and the generating unit 504 generates an AMP request according to the API access request in the following manner:
newly building a Fetch with the same name as the Fetch to obtain a newly built Fetch; defining attributes and methods with the same name as the Fetch in the newly-built Fetch; encapsulating a premium entrance outside the newly built Fetch, and suspending the sending of the API access request by using a premium asynchronous processing mechanism; analyzing the API access request in the newly-built Fetch to obtain an interface state query parameter, wherein the interface state query parameter is used for the AMP query service server to provide the interface state of a data interface requested by the API access request; renaming the Fetch to obtain a renamed Fetch; and combining the rename Fetch and the interface state query parameter to obtain the AMP request. The requesting unit 503 sends the API access request to the service server, and requests to obtain data requested by the API access request, in the following manner:
calling the rename Fetch, suspending the sent API access request, and sending the API access request to the service server.
In another possible implementation manner, the determining unit 501 is further configured to:
and before determining an API access request for requesting data from a service server, determining that a data request control is opened, wherein the data request control is used for sending the API access request to the service server and requesting to acquire the data requested by the API access request when indicating that the response identifier is determined to be received.
Based on the same inventive concept, the embodiment of the present invention also provides an apparatus for requesting data, which is applicable to the AMP.
As shown in fig. 6, an embodiment of the present invention provides an apparatus 600 for requesting data, and the apparatus 600 for requesting data is applicable to an AMP. The apparatus 600 for requesting data applied to an AMP includes a determining unit 601 and a transmitting unit 602. The determining unit 601 is configured to determine an interface state of a data interface requested by an API access request, and determine response data according to the interface state, where the response data is a response identifier for indicating to send the API access request to the service server when the interface state is in a development completion state. A sending unit 602, configured to return the response data.
The determining unit 601 determines the interface state of the data interface requested by the API access request by the following method:
obtaining an AMP request, wherein the AMP request is generated according to the API access request, is used for requesting to suspend sending of the API access request and is used for requesting the AMP to inquire the interface state of a data interface requested by the API access request; and determining the interface state of the data interface requested by the API access request according to the AMP request.
And when the interface state is in a development state, the response data is analog data fed back by the AMP.
It can be understood that the functions implemented by each module unit in the apparatus 500 for requesting data and the apparatus 600 for requesting data according to the embodiments of the present invention correspond to the steps in the method for requesting data described above, and for specific implementation and technical effects, reference is made to the description of the method steps above, and details are not described here.
It should be further understood that the structures of the apparatus 500 for requesting data and the apparatus 600 for requesting data (including the names and connection relationships of the module units) related to the above-mentioned embodiments of the present invention are only schematic illustrations, and the structures of the apparatus 500 for requesting data and the apparatus 600 for requesting data provided based on the same inventive concept as the method for requesting data related to the embodiments of the present invention are not limited to the structures shown in fig. 5 and 6, and are not limited to the structures including the above-mentioned module units, and may include other module units, or the above-mentioned module units may be further subdivided.
In some embodiments, the embodiment of the present invention further provides a server, which includes a memory and a processor. The memory is configured to store instructions. The processor is configured to invoke instructions to perform any of the methods described above.
In some embodiments, the present invention provides a computer-readable storage medium having stored thereon computer-executable instructions. The computer-executable instructions, when executed by the processor, perform any of the methods described above.
In some embodiments, the present invention further provides the following technical solutions:
scheme 1. a method of requesting data, wherein the method comprises:
determining an Application Program Interface (API) access request for requesting data from a service server;
receiving response data returned by an application program interface management platform (AMP), wherein the response data is determined by the AMP according to an interface state of a data interface requested by the API access request, and when the interface state is in a development completion state, the response data is a response identifier used for indicating that the API access request is sent to the service server;
and when the response identifier is determined to be received, sending the API access request to the service server, and requesting to acquire the data requested by the API access request.
Scheme 2. before receiving the response data returned by the application programming interface management platform AMP, the method according to scheme 1 further includes:
generating an AMP request according to the API access request, wherein the AMP request is used for suspending sending of the API access request and requesting the AMP to inquire the interface state of a data interface requested by the API access request;
sending the AMP request to an AMP.
Scheme 3. the method of scheme 2, wherein the response data is analog data fed back by the AMP when the interface state is in a development state.
Scheme 4. the method of scheme 2, wherein the API access request is determined by XM L http request,
generating an AMP request from the API access request, including:
creating an XM L HttpRequest with the same name as the XM L HttpRequest to obtain a new XM L HttpRequest, wherein the attributes and the method defined in the new XM L HttpRequest are the same as those of the XM L HttpRequest;
analyzing the API access request in an open method in the newly-built XM L HttpRequest to obtain an interface state query parameter, wherein the interface state query parameter is used for the AMP query service server to provide the interface state of a data interface requested by the API access request;
temporarily storing data required to be sent by the API access request in a send method of the newly-built XM L HttpRequest;
renaming the XM L HttpRequest to obtain a renamed XM L HttpRequest;
combining the renamed XM L HttpRequest with the interface state query parameter to obtain an AMP request;
the sending the API access request to the service server includes:
calling data which are needed to be sent by the API access request and temporarily stored in the send method of the newly-built XM L HttpRequest, and sending the API access request to the service server by using the renamed XM L HttpRequest.
Scheme 5. the method of scheme 2, wherein the API access request is determined by Fetch,
generating an AMP request from the API access request, including:
newly building a Fetch with the same name as the Fetch to obtain a newly built Fetch;
defining attributes and methods with the same name as the Fetch in the newly-built Fetch;
encapsulating a premium entrance outside the newly-built Fetch, and suspending the sending of the API access request by using a premium asynchronous processing mechanism;
analyzing the API access request in the newly-built Fetch to obtain an interface state query parameter, wherein the interface state query parameter is used for the AMP query service server to provide the interface state of a data interface requested by the API access request;
renaming the Fetch to obtain a renamed Fetch;
combining the rename Fetch with the interface state query parameter to obtain an AMP request;
the sending the API access request to the service server includes:
and calling the renamed Fetch and the API access request which is sent in a suspended mode, and sending the API access request to the service server.
Scheme 6. the method of any of schemes 1 to 5, wherein prior to determining the API access request for requesting data from the service server, the method further comprises:
and determining that a data request control is started, wherein the data request control is used for indicating to suspend sending the API access request when being started, and sending the API access request to the service server and requesting to acquire data requested by the API access request when determining to receive the response identifier.
A method of requesting data, wherein the method comprises:
determining the interface state of a data interface requested by an Application Program Interface (API) access request;
determining response data according to the interface state, wherein the response data is a response identifier for indicating to send the API access request to the service server when the interface state is in a development completion state;
and returning the response data.
Scheme 8. the method of scheme 7, wherein determining the interface state of the data interface requested by the API access request comprises:
obtaining an AMP request, wherein the AMP request is generated according to the API access request, is used for requesting to suspend sending of the API access request and is used for requesting the AMP to inquire the interface state of a data interface requested by the API access request;
and determining the interface state of the data interface requested by the API access request according to the AMP request.
Scheme 9. the method according to scheme 7 or 8, wherein the response data is analog data fed back by the AMP when the interface state is in a development state.
An apparatus for requesting data, wherein the apparatus comprises:
the system comprises a determining unit, a processing unit and a processing unit, wherein the determining unit is used for determining an Application Program Interface (API) access request for requesting data to a service server;
a receiving unit, configured to receive response data returned by an AMP, where the response data is determined by the AMP according to an interface state of a data interface requested by the API access request, and when the interface state is in a development completion state, the response data is a response identifier used to indicate that the API access request is sent to the service server;
and the request unit is used for sending the API access request to the service server and requesting to acquire the data requested by the API access request when the response identifier is determined to be received.
The apparatus of claim 10, wherein the apparatus further comprises a generating unit and a transmitting unit,
the generating unit is configured to generate an AMP request according to the API access request before the receiving unit receives response data returned by the AMP, where the AMP request is used to request to suspend sending of the API access request and is used to request the AMP to query an interface state of a data interface requested by the API access request;
the sending unit is used for sending the AMP request generated by the generating unit to the AMP.
Scheme 12. the apparatus of scheme 10, wherein the response data is analog data fed back by the AMP when the interface state is in a development state.
Scheme 13. the apparatus of scheme 11, wherein the API access request is determined by XM L http request,
the generating unit generates an AMP request from the API access request in the following manner:
creating an XM L HttpRequest with the same name as the XM L HttpRequest to obtain a new XM L HttpRequest, wherein the attributes and the method defined in the new XM L HttpRequest are the same as those of the XM L HttpRequest;
analyzing the API access request in an open method in the newly-built XM L HttpRequest to obtain an interface state query parameter, wherein the interface state query parameter is used for the AMP query service server to provide the interface state of a data interface requested by the API access request;
renaming the XM L HttpRequest to obtain a renamed XM L HttpRequest;
combining the renamed XM L HttpRequest with the interface state query parameter to obtain an AMP request;
the request unit sends the API access request to the service server in the following mode:
calling the data which is required to be requested by the API access request and is temporarily stored in the send method of the newly-built XM L HttpRequest, and sending the API access request to the service server by using the renamed XM L HttpRequest.
Scheme 14. the apparatus according to scheme 11, wherein the API access request is determined by Fetch, and the generating unit generates an AMP request from the API access request as follows:
newly building a Fetch with the same name as the Fetch to obtain a newly built Fetch;
defining attributes and methods with the same name as the Fetch in the newly-built Fetch;
encapsulating a premium entrance outside the newly-built Fetch, and suspending the sending of the API access request by using a premium asynchronous processing mechanism;
analyzing the API access request in the newly-built Fetch to obtain an interface state query parameter, wherein the interface state query parameter is used for the AMP query service server to provide the interface state of a data interface requested by the API access request;
renaming the Fetch to obtain a renamed Fetch;
combining the rename Fetch with the interface state query parameter to obtain an AMP request;
the request unit sends the API access request to the service server in the following mode:
and calling the renamed Fetch and the API access request which is sent in a suspended mode, and sending the API access request to the service server.
The apparatus according to any one of aspects 10 to 14, wherein the determining unit is further configured to:
before determining an API access request for requesting data from a service server, determining that a data request control is opened, wherein the data request control is used for indicating to suspend sending the API access request when being opened, and when determining to receive the response identifier, sending the API access request to the service server and requesting to acquire the data requested by the API access request.
An apparatus for requesting data, wherein the apparatus comprises:
the determining unit is used for determining the interface state of a data interface requested by an application program interface API access request, and determining response data according to the interface state, wherein the response data is a response identifier used for indicating to send the API access request to the service server when the interface state is in a development completion state;
and the sending unit is used for returning the response data.
Scheme 17. the apparatus according to scheme 16, wherein the determining unit determines the interface state of the data interface requested by the API access request as follows:
obtaining a request, wherein the AMP request is generated according to the API access request, is used for requesting to suspend sending of the API access request and is used for requesting the AMP to inquire the interface state of a data interface requested by the API access request;
and determining the interface state of the data interface requested by the API access request according to the AMP request.
Scheme 18. the apparatus of scheme 16 or 17, wherein the response data is analog data fed back by AMP when the interface state is in a development state.
A server, wherein the server comprises:
a memory configured to store instructions; and
a processor configured to invoke the instructions to perform the method of any of the above possible embodiments.
Scheme 20. a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions that, when executed by a processor, perform the method of any of the above possible embodiments.
It is to be understood that although the terms "first," "second," etc. may be used herein to describe various modules, steps, data, etc. of embodiments of the present invention, the terms "first," "second," etc. are used merely to distinguish between various modules, steps, data, etc., and do not denote a particular order or importance. Indeed, the terms "first," "second," and the like are fully interchangeable.
It is further to be understood that while operations are depicted in the drawings in a particular order, this is not to be understood as requiring that such operations be performed in the particular order shown or in serial order, or that all illustrated operations be performed, to achieve desirable results. In certain environments, multitasking and parallel processing may be advantageous.
The methods and apparatus of embodiments of the present invention can be accomplished using standard programming techniques with rule-based logic or other logic to accomplish the various method steps. It should also be noted that the words "means" and "module," as used herein and in the claims, is intended to encompass implementations using one or more lines of software code, and/or hardware implementations, and/or equipment for receiving inputs.
Any of the steps, operations, or procedures described herein may be performed or implemented using one or more hardware or software modules, alone or in combination with other devices. In one embodiment, the software modules are implemented using a computer program product comprising a computer readable medium containing computer program code, which is executable by a computer processor for performing any or all of the described steps, operations, or procedures.
The foregoing description of the implementation of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of the invention. The embodiments were chosen and described in order to explain the principles of the invention and its practical application to enable one skilled in the art to utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated.
Claims (16)
1. A method of requesting data, wherein the method comprises:
determining an Application Program Interface (API) access request for requesting data from a service server, when the API access request is determined by XM L HttpRequest, creating XM L HttpRequest with the same name as the XM L HttpRequest to obtain a new XM L HttpRequest, defining the attribute and method of the new XM L HttpRequest to be the same as the attribute and method of the XM L HttpRequest, analyzing the API access request in an open method in the new XM L HttpRequest to obtain an interface state query parameter, wherein the interface state query parameter is used for an application program interface management platform (AMP) to query a service server to provide the interface state of a data interface requested by the API access request, renaming the XM L HttpRequest to obtain a renamed XM L HttpRequest, and combining the rename XM L HttpRequest with the interface state query parameter to obtain the interface query request or obtain the AMP request,
when the API access request is determined by the Fetch, newly building the Fetch with the same name as the Fetch to obtain a newly built Fetch, defining an attribute and a method with the same name as the Fetch in the newly built Fetch, analyzing the API access request in the newly built Fetch to obtain an interface state query parameter, wherein the interface state query parameter is used for providing an interface state of a data interface requested by the API access request by an AMP query service server, renaming the Fetch to obtain a renamed Fetch, and combining the renamed Fetch and the interface state query parameter to obtain an AMP request;
the AMP request is used for suspending sending the API access request and requesting the AMP to inquire the interface state of a data interface requested by the API access request;
sending the AMP request to the AMP;
receiving response data returned by the AMP, wherein the response data is determined by the AMP according to an interface state of a data interface requested by the API access request, and when the interface state is in a development completion state, the response data is a response identifier used for indicating to send the API access request to the service server;
and when the response identifier is determined to be received, sending the API access request to the service server, and requesting to acquire the data requested by the API access request.
2. The method of claim 1, wherein the response data is analog data of the AMP feedback when the interface state is in a development state.
3. The method of claim 1, wherein when the API access request is determined by XM L HttpRequest, data required to be sent by the API access request is temporarily stored in the send method of the newly created XM L HttpRequest;
the sending the API access request to the service server includes:
calling data which are needed to be sent by the API access request and temporarily stored in the send method of the newly-built XM L HttpRequest, and sending the API access request to the service server by using the renamed XM L HttpRequest.
4. The method according to claim 1, wherein when the API access request is determined by Fetch, encapsulating a premium entry outside the newly-built Fetch, and suspending the sending of the API access request by using a premium asynchronous processing mechanism;
the sending the API access request to the service server includes:
and calling the renamed Fetch and the API access request which is sent in a suspended mode, and sending the API access request to the service server.
5. The method of any of claims 1 to 4, wherein prior to determining the API access request for requesting data from the service server, the method further comprises:
and determining that a data request control is started, wherein the data request control is used for indicating to suspend sending the API access request when being started, and sending the API access request to the service server and requesting to acquire data requested by the API access request when determining to receive the response identifier.
6. A method of requesting data, wherein the method comprises:
obtaining an application programming interface management platform (AMP) request, wherein the AMP request is determined by an Application Programming Interface (API) agent based on the API access request, wherein,
when an API access request is determined by XM L HttpRequest, the API agent creates an XM L0 HttpRequest with the same name as the XM L HttpRequest to obtain a new XM L HttpRequest, the attributes and methods defined in the new XM L HttpRequest are the same as those of the XM L HttpRequest, the API access request is analyzed in the open method in the new XM L HttpRequest to obtain an interface state query parameter, the interface state query parameter is used for a query service server to provide the interface state of a data interface requested by the API access request, data required to be sent by the API access request is temporarily stored in the send method of the new XM L HttpRequest, the XM L HttpRequest is renamed to obtain a rename XM L HttpRequest, the rename L HttpRequest is combined with the AMP query parameter, or the AMP query parameter is obtained,
when an API access request is determined by a Fetch, newly building a Fetch with the same name as the Fetch by the API agent to obtain a newly-built Fetch, defining an attribute and a method with the same name as the Fetch in the newly-built Fetch, encapsulating a premium entrance outside the newly-built Fetch, suspending the sending of the API access request by using a premium asynchronous processing mechanism, analyzing the API access request in the newly-built Fetch to obtain an interface state query parameter, wherein the interface state query parameter is used for providing an interface state of a data interface requested by the API access request by an AMP query service server, renaming the Fetch to obtain a renamed Fetch, and combining the renamed Fetch with the interface state query parameter to obtain an AMP request;
determining the interface state of a data interface requested by the API access request according to the AMP request;
determining response data according to the interface state, wherein when the interface state is in a development completion state, the response data is a response identifier for indicating to send the API access request to a service server, and the service server is used for receiving the API access request and returning the data requested by the API access request according to the API access request;
and returning the response data.
7. The method of claim 6, wherein the response data is analog data fed back by the AMP when the interface state is in a development state.
8. An apparatus for requesting data, wherein the apparatus comprises:
the system comprises a determining unit, a processing unit and a processing unit, wherein the determining unit is used for determining an Application Program Interface (API) access request for requesting data to a service server;
a generating unit, configured to, when the API access request is determined by an XM L http request, create an XM L http request having the same name as the XM L http request, obtain a new XM L http request, parse the API access request in an open method of the new XM 563 http request, obtain an interface state query parameter, where the interface state query parameter is used by an application program interface management platform AMP query service server to provide an interface state of a data interface requested by the API access request, rename the XM L http request, obtain a rename XM L http request, combine the rename XM L http request with the interface state query parameter, obtain an AMP request, and suspend the AMP request, and use the AMP request to send the API access request or the API access request to the data interface,
when the API access request is determined by the Fetch, newly building the Fetch with the same name as the Fetch to obtain a newly-built Fetch, defining an attribute and a method with the same name as the Fetch in the newly-built Fetch, analyzing the API access request in the newly-built Fetch to obtain an interface state query parameter, wherein the interface state query parameter is used for an AMP query service server to provide an interface state of a data interface requested by the API access request, renaming the Fetch to obtain a renamed Fetch, and combining the renamed Fetch and the interface state query parameter to obtain an AMP request, wherein the AMP request is used for pausing sending the API access request and requesting the AMP to query the interface state of the data interface requested by the API access request;
a transmitting unit for transmitting the AMP request to the AMP;
a receiving unit, configured to receive response data returned by the AMP, where the response data is determined by the AMP according to an interface state of a data interface requested by the API access request, and when the interface state is in a development completion state, the response data is a response identifier used to indicate that the API access request is sent to the service server;
and the request unit is used for sending the API access request to the service server and requesting to acquire the data requested by the API access request when the response identifier is determined to be received.
9. The apparatus of claim 8, wherein the response data is analog data of the AMP feedback when the interface state is in a development state.
10. The apparatus of claim 8, wherein the generating unit is to:
when the API access request is determined by XM L HttpRequest, temporarily storing data required to be sent by the API access request in a send method of the newly-built XM L HttpRequest, wherein the request unit sends the API access request to the service server in the following way:
calling the data which is required to be requested by the API access request and is temporarily stored in the send method of the newly-built XM L HttpRequest, and sending the API access request to the service server by using the renamed XM L HttpRequest.
11. The apparatus of claim 8, wherein the generating unit is to:
when the API access request is determined by the Fetch, encapsulating a premium entrance outside the newly-built Fetch, and suspending the sending of the API access request by using a premium asynchronous processing mechanism;
the request unit sends the API access request to the service server in the following mode:
and calling the renamed Fetch and the API access request which is sent in a suspended mode, and sending the API access request to the service server.
12. The apparatus according to any one of claims 8 to 11, wherein the determining unit is further configured to:
before determining an API access request for requesting data from a service server, determining that a data request control is opened, wherein the data request control is used for indicating to suspend sending the API access request when being opened, and when determining to receive the response identifier, sending the API access request to the service server and requesting to acquire the data requested by the API access request.
13. An apparatus for requesting data, wherein the apparatus comprises:
a determining unit, configured to obtain an application program interface management platform AMP request, where the AMP request is determined by an application program interface API proxy based on the API access request, where when the API access request is determined by XM L http request, the API proxy creates an XM L0 http request that is the same name as the XM L http request, obtains a new XM 567 http request, where attributes and methods defined in the new XM L http request are the same as those of the XM 68 http request, parses the API access request in an openmethod in the new XM L http request, obtains an interface state query parameter, where the interface state query parameter is used for an AMP query service server to provide an interface state of a data interface requested by the API access request, temporarily stores data required to be sent by the API access request in an XM L http signed method, renames the data interface state query request, renames the http 352, renames the http response request, obtains the http response status of the http response request, renames the API query request, obtains the http response status of the http response request, renames the http response status of the API 3536, renames the API response request, obtains the response status of the API proxy, obtains the API proxy, renames the response status of the API proxy L, obtains the API proxy, obtains the response status of the API proxy, obtains the,
when API access request is determined through Fetch, API agent newly-built with Fetch with the same name obtains newly-built Fetch, define in newly-built Fetch with the same name's attribute and method newly-built Fetch encapsulate the premium entry outside newly-built Fetch to utilize the asynchronous processing mechanism of premium, suspend the sending of API access request parse in newly-built Fetch API access request obtains interface state inquiry parameter, interface state inquiry parameter is used for AMP inquiry service server to provide the interface state of API access request data interface, rename Fetch obtains rename Fetch, will rename Fetch with interface state inquiry parameter combination obtains the AMP request to and AMP inquiry service server provides
A determining unit, configured to determine, according to the AMP request, an interface state of a data interface requested by the API access request, and determine, according to the interface state, response data, where the interface state is in a development completion state, the response data is a response identifier used to indicate that an API access request is sent to a service server, and the service server is used to receive the API access request and return data requested by the API access request according to the API access request;
and the sending unit is used for returning the response data.
14. The apparatus of claim 13, wherein the response data is analog data fed back by an AMP when the interface state is in a development state.
15. A server, wherein the server comprises:
a memory configured to store instructions; and
a processor configured to invoke the instructions to perform a method of requesting data according to any one of claims 1 to 7.
16. A computer-readable storage medium having stored thereon computer-executable instructions which, when executed by a processor, perform a method of requesting data as recited in any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811019472.6A CN109218297B (en) | 2018-08-31 | 2018-08-31 | Method and device for requesting data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811019472.6A CN109218297B (en) | 2018-08-31 | 2018-08-31 | Method and device for requesting data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109218297A CN109218297A (en) | 2019-01-15 |
| CN109218297B true CN109218297B (en) | 2020-08-07 |
Family
ID=64986687
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811019472.6A Active CN109218297B (en) | 2018-08-31 | 2018-08-31 | Method and device for requesting data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109218297B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110413526A (en) * | 2019-07-30 | 2019-11-05 | 北京达佳互联信息技术有限公司 | A kind of request processing method, device, server and equipment |
| CN114065274A (en) * | 2020-08-07 | 2022-02-18 | 伊姆西Ip控股有限责任公司 | Method, electronic device and computer program product for processing information |
| CN115623079B (en) * | 2022-12-19 | 2023-06-02 | 中科政汇(北京)科技有限公司 | Data access processing method |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103699367A (en) * | 2012-09-27 | 2014-04-02 | 中国电信股份有限公司 | HTTP (hyper text transport protocol) API (application program interface) invoking method and device |
| CN105847444A (en) * | 2016-05-31 | 2016-08-10 | 广东能龙教育股份有限公司 | Interface simulation method based on proxy service |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9396091B2 (en) * | 2014-09-29 | 2016-07-19 | Sap Se | End-to end, lifecycle aware, API management |
| CN106776313B (en) * | 2016-12-13 | 2020-06-23 | 广州品唯软件有限公司 | Method, device and centralized management platform for simulating service |
-
2018
- 2018-08-31 CN CN201811019472.6A patent/CN109218297B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103699367A (en) * | 2012-09-27 | 2014-04-02 | 中国电信股份有限公司 | HTTP (hyper text transport protocol) API (application program interface) invoking method and device |
| CN105847444A (en) * | 2016-05-31 | 2016-08-10 | 广东能龙教育股份有限公司 | Interface simulation method based on proxy service |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109218297A (en) | 2019-01-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2976709B1 (en) | Systems and methods for intercepting, processing, and protecting user data through web application pattern detection | |
| KR102220127B1 (en) | Method and apparatus for customized software development kit (sdk) generation | |
| US8656452B2 (en) | Data assurance | |
| EP2798494B1 (en) | Virtual channel for embedded process communication | |
| RU2648966C2 (en) | Apparatus and method for processing multiple open api | |
| KR100843581B1 (en) | Extending markup of a browser using a plug-in framework | |
| US8332520B2 (en) | Web server for managing session and method thereof | |
| US8549471B2 (en) | Method and apparatus for providing API service and making API mash-up, and computer readable recording medium thereof | |
| US8341239B2 (en) | Method and system for providing runtime vulnerability defense for cross domain interactions | |
| CN104427627B (en) | Test data acquisition methods, client and server | |
| US20170046135A1 (en) | Configurable Development Platform Integrating Heterogeneous Persistence Systems | |
| US9086935B2 (en) | Accessing business object resources for a machine-to-machine communication environment | |
| US9143378B2 (en) | Rendering components within different browser environments | |
| CN109218297B (en) | Method and device for requesting data | |
| US10031971B2 (en) | System and methods for optimizing the response to a request for dynamic web content | |
| CN109343975B (en) | Method and apparatus for inter-page asynchronous communication | |
| US20100229081A1 (en) | Method for Providing a Navigation Element in an Application | |
| TW201409273A (en) | Method and Apparatus of Responding to Webpage Access Request | |
| US20120117491A1 (en) | Web interface for remote platform build | |
| CN111767109A (en) | H5 page display method, device and readable storage medium based on terminal application | |
| JP5347429B2 (en) | Uniform resource locator rewriting method and apparatus | |
| WO2021093672A1 (en) | Method for embedding external system, workflow system, device and computer readable storage medium | |
| US10165022B1 (en) | Screen sharing management | |
| CN105786476B (en) | Data processing method and system between mobile client and server | |
| US20160357715A1 (en) | Mechanisms to support multi-service hyperlink pipelines in web browser |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |