CN112905254B

CN112905254B - Method and device for sending request

Info

Publication number: CN112905254B
Application number: CN201911119768.XA
Authority: CN
Inventors: 黄运智
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2019-11-15
Filing date: 2019-11-15
Publication date: 2023-10-31
Anticipated expiration: 2039-11-15
Also published as: CN112905254A

Abstract

Embodiments of the present disclosure relate to the field of data request technology. The embodiment of the disclosure discloses a method and a device for sending a request. One embodiment of the method comprises the following steps: acquiring a request to be packaged generated in a target application; the method comprises the steps that a first plugin corresponding to a target application in a preset first plugin set is utilized to carry out packaging processing before sending on a request to be packaged to obtain the request to be sent, wherein the first plugin set is preset in a requester, and the requester is preset to carry out packaging processing on the request to be packaged generated by the target application; and sending the request to be sent to a server. The embodiment of the disclosure can utilize the plug-in to rapidly expand the functions of the requester and ensure that the coupling degree of the expanded content and each module is low. In addition, by the plug-in, more flexibility in adding or deleting functions in the requester can be achieved.

Description

Method and device for sending request

Technical Field

The embodiment of the disclosure relates to the technical field of computers, in particular to the technical field of Internet, and particularly relates to a method and a device for sending a request.

Background

The user often needs to interact with the server when using various applications on the terminal device. In the process of interaction, the terminal device often sends a request.

If a complete, transmittable request is to be generated at the terminal device, more requesters associated with the request often need to be written for additional expansion. And a large amount of core codes are required to be added in the expansion, so that the execution difficulty is high, and the coupling degree of the content in the requester and each model is high.

Disclosure of Invention

The embodiment of the disclosure provides a method and a device for sending a request.

In a first aspect, an embodiment of the present disclosure provides a method for sending a request, including: acquiring a request to be packaged generated in a target application; the method comprises the steps that a first plugin corresponding to a target application in a preset first plugin set is utilized to perform packaging processing before sending a request to be packaged to obtain the request to be sent, wherein the first plugin set is preset in a requester, and the requester is preset to perform packaging processing on the request to be packaged generated by the target application; and sending a request to be sent to a server.

In some embodiments, the first set of plugins includes a first plugin queue; and performing packaging processing before sending a request to be packaged by using a first plugin corresponding to a target application in a preset first plugin set, wherein the packaging processing comprises the following steps: and responding to the request to be packaged, wherein the request to be packaged comprises the identification of the target application, and operating at least one first plugin which is preset and is used for packaging the request to be packaged of the target application in the first plugin queue by calling a designated processing method in a requester corresponding to the identification of the target application.

In some embodiments, a first card in the first card set includes a first parameter indicating to the first card to process the content of the request to be packaged and a second parameter indicating to operate a next card in the at least one first card in the order of the at least one first card in the first card queue in response to the first card being operated.

In some embodiments, the method further comprises: setting calling state information of a second parameter for a first plugin in a first plugin set, wherein the calling state information comprises first state information representing that the second parameter is called after the first plugin is operated, or second state information representing that the second parameter is not called after the first plugin is operated; and running at least one first plugin which is preset and is used for carrying out packaging processing on the request to be packaged of the target application in the first plugin queue, and sequentially carrying out packaging processing on the request to be packaged, wherein the method comprises the following steps: responding to the calling state information of the second parameter of the first plugin as first state information, and if the first plugin is finished running, running the next plugin of the first plugin according to the sequence of the at least one first plugin in the first plugin queue; and responding to the calling state information of the second parameter of the first plugin as second state information, if the first plugin is finished running, intercepting a request obtained by running the first plugin for packaging processing, and stopping packaging processing of the request in a requester.

In some embodiments, the method further comprises: setting a call-free condition of a second parameter for a first plugin in a first plugin set, wherein the call-free condition comprises that a request of current encapsulation processing of the first plugin is the same as a request of previous encapsulation processing, and the interval time of encapsulation processing does not reach a preset threshold; and running at least one first plugin which is preset and is used for carrying out packaging processing on the request to be packaged of the target application in the first plugin queue, and sequentially carrying out packaging processing on the request to be packaged, wherein the method comprises the following steps: and responding to the first plugin meeting the call-free condition, if the first plugin is finished running, intercepting a request obtained by the first plugin for packaging, and stopping packaging of the request in a requester.

In some embodiments, the method further comprises: responding to a detection instruction for adding a plug-in to be added of a target application into a first plug-in set, and obtaining the plug-in to be added, wherein the plug-in to be added is a plug-in except for the plug-in the first plug-in set, and the plug-in to be added is a plug-in for packaging a request to be packaged of the target application; adding the plug-in to be added into the first plug-in set by calling a specified adding method in a requester corresponding to the identification of the target application; determining a plug-in to be deleted according to a detection instruction for indicating the plug-in to be deleted of the target application from the first plug-in set, wherein the plug-in to be deleted is a plug-in the first plug-in set, and the plug-in to be added is a plug-in for packaging a request to be packaged of the target application; and deleting the plug-in to be deleted from the first plug-in set by calling a specified deletion method in the requester corresponding to the identification of the target application.

In some embodiments, the requestor is further preconfigured to pre-utilize the response information for the target application, the method further comprising: receiving response information which is fed back by a server and aims at a target application; and utilizing a second plugin corresponding to the target application in a preset second plugin set to pre-process the response information and transmit a processing result to the target application, wherein the second plugin set is preset in the requester.

In some embodiments, the second set of plugins includes a second plugin queue; and utilizing a second plugin corresponding to the target application in the preset second plugin set to perform utilization pretreatment on the response information, wherein the utilization pretreatment comprises the following steps: and responding to the response information comprising the identification of the target application, and operating at least one second plugin in the second plugin queue, which is preset and used for carrying out utilization pretreatment on the response information of the target application, by calling a designated processing method in a requester corresponding to the identification of the target application, so as to sequentially carry out utilization pretreatment on the response information.

In some embodiments, the second plugin in the second plugin set includes a first parameter and a second parameter, the second parameter indicating the content of the second plugin to be processed for the response information, the second parameter indicating that in response to the second plugin being completed, a next plugin of the at least one second plugin is executed in the order of the at least one second plugin in the second plugin queue.

In some embodiments, the method further comprises: setting calling state information of a second parameter for a second plugin in a second plugin set, wherein the calling state information comprises first state information representing that the second parameter is called after the second plugin is operated, or second state information representing that the second parameter is not called after the second plugin is operated; and running at least one second plugin for carrying out utilization pretreatment on response information of the target application in the second plugin queue, wherein the preset second plugin is used for carrying out utilization pretreatment on the response information in sequence and comprises the following steps: responding to the calling state information of the second parameter of the second plugin as second state information, and if the second plugin is finished running, running the next plugin of the second plugin according to the sequence of the at least one second plugin in the second plugin queue; and responding to the calling state information of the second parameter of the second plug-in as second state information, if the second plug-in is finished running, intercepting the response information obtained by running the second plug-in for utilizing the preprocessing, and stopping the utilizing preprocessing of the response information in the requester.

In some embodiments, the method further comprises: setting a call-free condition of a second parameter for a second plugin in a second plugin set, wherein the call-free condition comprises that a request of the second plugin for current encapsulation processing is the same as a request of the previous encapsulation processing, and the interval time of the encapsulation processing does not reach a preset threshold; and running at least one second plugin for carrying out utilization pretreatment on response information of the target application in the second plugin queue, wherein the preset second plugin is used for carrying out utilization pretreatment on the response information in sequence and comprises the following steps: and if the second plug-in meets the call-free condition, intercepting and operating the response information obtained by the second plug-in for utilizing the preprocessing and stopping the utilizing preprocessing of the response information in the requester.

In some embodiments, the method further comprises: responding to the detection instruction to add the plug-in to be added of the target application to the second plug-in set, and obtaining the plug-in to be added, wherein the plug-in to be added is a plug-in except for the plug-in the second plug-in set, and the plug-in to be added is a plug-in for performing utilization preprocessing on response information of the target application; adding the plug-in to be added into the second plug-in set by calling a specified adding method in the requester corresponding to the identification of the target application; determining a plug-in to be deleted according to the instruction of the plug-in to be deleted, which indicates the target application, from the second plug-in set, wherein the plug-in to be deleted is a plug-in the second plug-in set, and the plug-in to be added is a plug-in for performing utilization preprocessing on response information of the target application; and deleting the plug-in to be deleted from the second plug-in set by calling a specified deletion method in the requester corresponding to the identification of the target application.

In a second aspect, an embodiment of the present disclosure provides an apparatus for transmitting a request, including: an acquisition unit configured to acquire a request to be packaged generated in a target application; the packaging unit is configured to utilize a first plugin corresponding to the target application in a preset first plugin set to perform packaging processing before sending the request to be packaged to obtain the request to be sent, wherein the first plugin set is preset in a requester, and the requester is configured to perform packaging processing on the request to be packaged generated by the target application in advance; and a transmitting unit configured to transmit a request to be transmitted to the server.

In some embodiments, the first set of plugins includes a first plugin queue; and a packaging unit configured to perform packaging processing before sending the request to be packaged by using a first plug-in corresponding to the target application in the preset first plug-in set in the following manner: and responding to the request to be packaged, wherein the request to be packaged comprises the identification of the target application, and operating at least one first plugin which is preset and is used for packaging the request to be packaged of the target application in the first plugin queue by calling a designated processing device in a requester corresponding to the identification of the target application.

In some embodiments, the apparatus further comprises: the first setting unit is configured to set calling state information of a second parameter for a first plugin in the first plugin set, wherein the calling state information comprises first state information representing that the second parameter is called after the first plugin is operated, or second state information representing that the second parameter is not called after the first plugin is operated; and the packaging unit is further configured to execute at least one first plug-in which is preset and is used for packaging the request to be packaged of the target application in the first plug-in queue, and sequentially perform packaging processing on the request to be packaged: responding to the calling state information of the second parameter of the first plugin as first state information, and if the first plugin is finished running, running the next plugin of the first plugin according to the sequence of the at least one first plugin in the first plugin queue; and responding to the calling state information of the second parameter of the first plugin as second state information, if the first plugin is finished running, intercepting a request obtained by running the first plugin for packaging processing, and stopping packaging processing of the request in a requester.

In some embodiments, the apparatus further comprises: the second setting unit is configured to set a call-free condition of a second parameter for a first plugin in the first plugin set, wherein the call-free condition comprises that a request of current encapsulation processing of the first plugin is the same as a request of previous encapsulation processing, and the interval time of encapsulation processing does not reach a preset threshold; and the packaging unit is further configured to execute at least one first plug-in which is preset and is used for packaging the request to be packaged of the target application in the first plug-in queue, and sequentially perform packaging processing on the request to be packaged: and responding to the first plugin meeting the call-free condition, if the first plugin is finished running, intercepting a request obtained by the first plugin for packaging, and stopping packaging of the request in a requester.

In some embodiments, the apparatus further comprises: the first adding unit is configured to respond to the detection of an instruction for indicating to add the plug-in to be added of the target application into the first plug-in set, and obtain the plug-in to be added, wherein the plug-in to be added is a plug-in except for the plug-in the first plug-in set, and the plug-in to be added is a plug-in for packaging processing of a request to be packaged of the target application; adding the plug-in to be added into the first plug-in set by calling a designated adding device in a requester corresponding to the identification of the target application; the first deleting unit is configured to respond to the detection of an instruction for deleting the plug-in to be deleted of the target application from the first plug-in set, and the plug-in to be deleted is a plug-in the first plug-in set and is a plug-in for packaging a request to be packaged of the target application; and deleting the plug-in to be deleted from the first plug-in set by calling a designated deleting device in the requester corresponding to the identification of the target application.

In some embodiments, the requestor is further preconfigured to pre-utilize the response information for the target application, the apparatus further comprising: the receiving unit is configured to receive response information, fed back by the server, of the target application; and the pre-processing unit is configured to perform pre-processing on the response information by using a second plugin corresponding to the target application in a preset second plugin set, and transmit a processing result to the target application, wherein the second plugin set is preset in the requester.

In some embodiments, the second set of plugins includes a second plugin queue; and a pre-utilization processing unit, further configured to perform pre-utilization processing on the response information by using a second plug-in corresponding to the target application in the preset second plug-in set in the following manner: and responding to the response information comprising the identification of the target application, and operating at least one second plugin in the second plugin queue, which is preset and used for carrying out utilization pretreatment on the response information of the target application, by calling a designated processing device in a requester corresponding to the identification of the target application, so as to sequentially carry out utilization pretreatment on the response information.

In some embodiments, the apparatus further comprises: the third setting unit is configured to set calling state information of a second parameter for a second plugin in the second plugin set, wherein the calling state information comprises first state information representing that the second parameter is called after the second plugin is operated, or second state information representing that the second parameter is not called after the second plugin is operated; and a pre-utilization processing unit, further configured to execute at least one second plug-in preset for performing pre-utilization processing on response information of the target application in the second plug-in queue, and sequentially perform pre-utilization processing on the response information: responding to the calling state information of the second parameter of the second plugin as second state information, and if the second plugin is finished running, running the next plugin of the second plugin according to the sequence of the at least one second plugin in the second plugin queue; and responding to the calling state information of the second parameter of the second plug-in as second state information, if the second plug-in is finished running, intercepting the response information obtained by running the second plug-in for utilizing the preprocessing, and stopping the utilizing preprocessing of the response information in the requester.

In some embodiments, the apparatus further comprises: a fourth setting unit, configured to set a call-free condition of a second parameter for a second plugin in the second plugin set, where the call-free condition includes that a request of a current package process of the second plugin is the same as a request of a previous package process, and an interval time of the package process does not reach a preset threshold; and a pre-utilization processing unit, further configured to execute at least one second plug-in preset for performing pre-utilization processing on response information of the target application in the second plug-in queue, and sequentially perform pre-utilization processing on the response information: and if the second plug-in meets the call-free condition, intercepting and operating the response information obtained by the second plug-in for utilizing the preprocessing and stopping the utilizing preprocessing of the response information in the requester.

In some embodiments, the apparatus further comprises: the second adding unit is configured to respond to the detection of an instruction for indicating to add the plug-in to be added of the target application into the second plug-in set, and obtain the plug-in to be added, wherein the plug-in to be added is a plug-in except for the plug-in the second plug-in set, and the plug-in to be added is a plug-in for performing utilization preprocessing on response information of the target application; adding the plug-in to be added into the second plug-in set by calling a specified adding method in the requester corresponding to the identification of the target application; the second deleting unit is configured to respond to the detection of an instruction for deleting the plug-in to be deleted of the target application from the second plug-in set, and the plug-in to be deleted is a plug-in the second plug-in set and is a plug-in for performing utilization preprocessing on response information of the target application; and deleting the plug-in to be deleted from the second plug-in set by calling a specified deletion method in the requester corresponding to the identification of the target application.

In a third aspect, an embodiment of the present disclosure provides an electronic device, including: one or more processors; and a storage means for storing one or more programs that, when executed by the one or more processors, cause the one or more processors to implement a method as in any of the embodiments of the method for sending a request.

In a fourth aspect, the disclosed embodiments provide a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a method as any of the embodiments of the method for sending a request.

The scheme for sending the request provided by the embodiment of the disclosure firstly obtains a request to be packaged, which is generated in a target application. And then, carrying out packaging processing before sending the request to be packaged by utilizing a first plugin corresponding to the target application in a preset first plugin set to obtain the request to be sent, wherein the first plugin set is preset in a requester, and the requester is preset to carry out packaging processing on the request to be packaged generated by the target application. And finally, sending a request to be sent to the server. The embodiment of the disclosure can utilize the plug-in to rapidly expand the function of the requester and ensure that the coupling degree of the expanded content and each module is low.

Drawings

Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the accompanying drawings in which:

FIG. 1 is an exemplary system architecture diagram in which some embodiments of the present application may be applied;

FIG. 2 is a flow chart of one embodiment of a method for sending a request in accordance with the present application;

FIG. 3 is a flow chart of yet another embodiment of a method for sending a request in accordance with the present application;

FIG. 4 is a flow chart of yet another embodiment of a method for sending a request in accordance with the present application;

FIG. 5 is a flow chart of yet another embodiment of a method for sending a request in accordance with the present application;

FIG. 6 is a schematic diagram illustrating the structure of one embodiment of an apparatus for sending a request in accordance with the present application;

FIG. 7 is a schematic diagram of a computer system suitable for use in implementing some embodiments of the application.

Detailed Description

The application is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. It should be noted that, for convenience of description, only the portions related to the present application are shown in the drawings.

It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other. The application will be described in detail below with reference to the drawings in connection with embodiments.

Fig. 1 shows an exemplary system architecture 100 to which embodiments of the method for sending a request or the apparatus for sending a request of the present application may be applied.

As shown in fig. 1, a system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The user may interact with the server 105 via the network 104 using the terminal devices 101, 102, 103 to receive or send messages or the like. Various communication client applications, such as an application for web browsing, a video-type application, a live application, an instant messaging tool, a mailbox client, social platform software, etc., may be installed on the terminal devices 101, 102, 103.

The terminal devices 101, 102, 103 may be hardware or software. When the terminal devices 101, 102, 103 are hardware, they may be various electronic devices with display screens, including but not limited to smartphones, tablets, electronic book readers, laptop and desktop computers, and the like. When the terminal devices 101, 102, 103 are software, they can be installed in the above-listed electronic devices. Which may be implemented as multiple software or software modules (e.g., multiple software or software modules for providing distributed services) or as a single software or software module. The present application is not particularly limited herein.

The server 105 may be a server providing various services, such as a background server providing support for the terminal devices 101, 102, 103. The background server may analyze and process the received data such as the request to be sent, and feed back the processing result (for example, response information) to the terminal device.

It should be noted that the method for sending a request provided by the embodiment of the present application may be performed by the terminal devices 101, 102, 103, and accordingly, the means for sending a request may be provided in the terminal devices 101, 102, 103.

It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

With continued reference to FIG. 2, a flow 200 of one embodiment of a method for sending a request in accordance with the present application is shown. The method for transmitting a request comprises the steps of:

step 201, a request to be encapsulated generated in a target application is obtained.

In this embodiment, an execution body of the method for transmitting a request (for example, the terminal device shown in fig. 1) may acquire a request to be encapsulated. The device may be installed with a plurality of applications, where the request to be encapsulated is generated in a target application of the plurality of applications. The request to be packaged refers to a request to be subjected to packaging processing. For example, the request to be encapsulated may include a request header, an identification of an application, an address of a target server to be sent to, and the like. The encapsulation processing of the request to be encapsulated herein may refer to combining the data and the functions of the request to be encapsulated to form a whole, and hiding the attribute and implementation details of the data, and only disclosing the interface externally. In practice, the encapsulation process may include a format modification of the parameter values of the request header, such as a modification of the format of the parameter values of the request header to a specified format, which may be JSON (JavaScript Object Notation) format, for example. The encapsulation process may further include adding a specific tag to the request to be encapsulated, so that the server performs special processing on the request with the specific tag.

Step 202, performing packaging processing before sending a request to be packaged by using a first plugin corresponding to a target application in a preset first plugin set to obtain the request to be sent, wherein the first plugin set is preset in a requester, and the requester is preset to perform packaging processing on the request to be packaged generated by the target application.

In this embodiment, the executing body may perform encapsulation processing on the obtained request to be encapsulated by using the plugins in the first plugin set, so that the request to be encapsulated is processed into the request to be sent, so as to facilitate sending. The plug-ins in the first set of plug-ins may be referred to as first plug-ins, which plug-ins correspond to the target application. The correspondence here refers to that the first plug-in is used to process a request to be encapsulated generated at the target application. It should be noted that, in some cases, the first plug-in may not only perform the encapsulation processing on the request to be encapsulated, but also perform other processing operations. The first set of plugins present in the above-described requestor may be implemented as a plugin pool.

The requester is a software module provided in the terminal device and can be used for further processing (such as encapsulation processing) the request generated initially in the application, so as to obtain a transmittable request. In the terminal device, each application may have a corresponding requester, and the requesters of different applications are isolated from each other. In addition, the requester can also process response information of the server for requesting feedback.

In practice, the encapsulation processing operations performed by each first plug-in the first set of plug-ins for an encapsulation request may be different, each of which may perform one or more encapsulation processing operations. For example, one first plug-in may convert the format of the request to be packaged and the other first plug-in may tag the request to be packaged specifically.

Step 203, a request to be sent is sent to a server.

In this embodiment, the execution body may send the request to be sent, which is obtained by the encapsulation processing, to the server. In particular, the request herein may be various requests related to the application, for example, an update request of the application, or a request related to the page, such as a request for display data of the page, or an update request of the page, or the like.

In some optional implementations of this embodiment, the method may further include: responding to a detection instruction for adding a plug-in to be added of a target application into a first plug-in set, and obtaining the plug-in to be added, wherein the plug-in to be added is a plug-in except for the plug-in the first plug-in set, and the plug-in to be added is a plug-in for packaging a request to be packaged of the target application; adding the plug-in to be added into the first plug-in set by calling a specified adding method in a requester corresponding to the identification of the target application; determining a plug-in to be deleted according to a detection instruction for indicating the plug-in to be deleted of the target application from the first plug-in set, wherein the plug-in to be deleted is a plug-in the first plug-in set, and the plug-in to be added is a plug-in for packaging a request to be packaged of the target application; and deleting the plug-in to be deleted from the first plug-in set by calling a specified deletion method in the requester corresponding to the identification of the target application.

In these alternative implementations, the execution body may adjust the plug-ins in the first set of plug-ins by invoking methods in various application program interfaces (Application Programming Interface, APIs). For example, if a locally generated or other instruction sent by the electronic device to instruct to add the plug-in to be added is detected, the execution body may call a preset method, such as use (), to add the plug-in to be added to the first plug-in set. In addition, if a command indicating to delete a plug-in to be deleted, which is generated locally or sent by other electronic devices, is detected, the execution body may call a preset method, such as an abart (), and delete the plug-in to be deleted from the first plug-in set.

For example, in a requestor that processes an application, there are 10 plugins in a first plugin queue, where the 6 th plugin is a plugin for adding a specific tag, and if the specific tag is not required to be added, the 6 th plugin can be deleted from the first plugin queue. After deletion, 9 cards remain in the first card queue. If a developer were to add another tag to the application's request, a plug-in for adding the other tag may be added to the first plug-in queue.

These alternative implementations may flexibly adjust the plugins in the requester to enable more accurate encapsulation of requests to be encapsulated.

The method provided by the embodiment of the application can utilize the plug-in to rapidly expand the functions of the requester and ensure that the coupling degree of the expanded content and each module is low. In addition, by the plug-in, more flexibility in adding or deleting functions in the requester can be achieved.

With further reference to fig. 3, a flow 300 of yet another embodiment of a method for sending a request is shown. The flow 300 of the method for sending a request comprises the steps of:

step 301, a request to be encapsulated generated in a target application is obtained.

In this embodiment, an execution body of the method for transmitting a request (for example, the terminal device shown in fig. 1) may acquire a request to be encapsulated. The device may be installed with a plurality of applications, where the request to be encapsulated is generated in a target application of the plurality of applications. The request to be packaged refers to a request to be subjected to packaging processing. The encapsulation processing of the request to be encapsulated herein may refer to combining the data and the functions of the request to be encapsulated to form a whole, and hiding the attribute and implementation details of the data, and only disclosing the interface externally.

Step 302, in response to the request to be packaged including the identifier of the target application, running at least one first plugin preset for performing packaging processing on the request to be packaged of the target application in the first plugin queue by calling a designated processing method in a requester corresponding to the identifier of the target application, and sequentially performing packaging processing on the request to be packaged to obtain the request to be sent.

In this embodiment, the first set of plugins includes a first plugin queue. The execution body may run at least one first plug-in the first plug-in queue in the requester in response to the request to be encapsulated including the identifier of the target application, and perform encapsulation processing on the request to be encapsulated in sequence. The sequential processing refers to that the encapsulation processing result output by one plug-in is input into the other plug-in for encapsulation processing. In the at least one first plug-in, each first plug-in is cascaded.

Specifically, the execution body may implement the operation of the first plugin by calling a specified processing method, such as handle (), in the requester corresponding to the identifier of the target application, that is, the requester configured in advance to perform the encapsulation processing on the request to be encapsulated generated by the target application.

In practice, the first cards in the requester may be arranged in a queue, thereby arranging into a first card queue. In particular, the cards in the first card queue may be arranged according to various rules, for example, may be arranged according to the time sequence in which the cards are added to the card queue. Further, the placement of some or all of the cards in the first card queue may be developer-specified.

The at least one first plugin may include all plugins in the first plugin queue, so the execution body may allow the request to be packaged to sequentially pass through all the first plugins in the first plugin queue according to the arrangement order of the first plugins in the queue. In some cases, the at least one first plugin may include only a part of plugins in the first plugin queue, so the execution body may process the request to be encapsulated sequentially according to the arrangement order of the part of plugins in the first plugin queue by using only the part of plugins in the first plugin queue.

In some optional implementations of this embodiment, a first card in the first card set includes a first parameter indicating that the first card is to process content of a request to be packaged and a second parameter indicating that, in response to the first card being running, a next card in the at least one first card is to be run in the order of the at least one first card in the first card queue.

In these alternative implementations, a first plug-in the first set of plug-ins may contain a first parameter, such as options (), and may also contain a second parameter, such as next (). In practice, the first parameter and the second parameter may be called as methods by the execution body described above. For each first plugin, the first parameter indicates the content to be processed of the request to be packaged by the first plugin. The content to be processed may be a parameter in the request, for example, may be a parameter in a request header, or may be a parameter related to a tag carried by the request, etc. The second parameter indicates that the next plug-in is to be run if the first plug-in is run. The next card here may be a first card adjacent to the first card in the first card queue. In this way, the executing body may sequentially run all the cards in the first card queue to process the request to be encapsulated by using the second parameter in each card.

The implementation mode can accurately and orderly operate each plug-in through the first parameter and the second parameter, and clear the content to be processed in the request, and process the request to be packaged in a targeted manner.

Optionally, before step 301, the method may further include: setting calling state information of a second parameter for a first plugin in a first plugin set, wherein the calling state information comprises first state information representing that the second parameter is called after the first plugin is operated, or second state information representing that the second parameter is not called after the first plugin is operated; and in the running first plug-in queue in step 302, at least one first plug-in preset for performing packaging processing on a request to be packaged of a target application, and sequentially performing packaging processing on the request to be packaged may include: responding to the calling state information of the second parameter of the first plugin as first state information, and if the first plugin is finished running, running the next plugin of the first plugin according to the sequence of the at least one first plugin in the first plugin queue; and responding to the calling state information of the second parameter of the first plugin as second state information, if the first plugin is finished running, intercepting a request obtained by running the first plugin for packaging processing, and stopping packaging processing of the request in a requester.

In this alternative implementation, for a first plug-in the first plug-in queue, the execution body may set call state information of the second parameter for the first plug-in. The parameter values herein may include first state information and second state information. Specifically, the first state information may be used to indicate that the second parameter is called after the first plug-in is finished running, and the second state information may be used to indicate that the second parameter is not called after the first plug-in is finished running.

In the case that the call state information is the first state information, the execution body may run all the plugins in the first plugin queue to perform encapsulation processing on the request to be encapsulated. After the first plug-in is operated to perform the encapsulation, the next plug-in may be used to perform further encapsulation on the request after the encapsulation of the first plug-in. And in the case that the call state information is the second state information, the at least one preset first plugin for performing the encapsulation processing on the request to be encapsulated of the target application may be only a part of plugins in the first plugin queue. Then, after the first plug-in unit runs, the executing body may intercept the request obtained after the first plug-in unit encapsulates the request to be encapsulated, and terminate the encapsulation of the request in the requester. In practice, after the package processing is suspended, the executing body may directly use the request obtained by the package processing of the first plugin as a request to be sent, or may recall the processing method specified in the requester, and execute, based on the information indicating the at least one first plugin pre-stored in the requester, the plugin in the at least one first plugin, where the plugin is arranged after the first plugin in the first plugin queue, to continue the package processing on the request obtained last before the suspension.

For example, there are 10 plug-ins in the first plug-in queue, where the 5 th plug-in, i.e. the 5 th plug-in, encapsulates a certain request to be encapsulated, and if the calling state information of the second parameter of the 5 th plug-in is the first state information, the executing body may call the second parameter of the 5 th plug-in to execute the 6 th plug-in to continue encapsulating the request obtained by the 5 th plug-in when the 5 th plug-in encapsulates the request to be encapsulated. If the calling state information of the second parameter of the plug-in No. 5 is the second state information, the execution body may intercept the result of the encapsulation processing of the request by the plug-in No. 5 and terminate the encapsulation processing of the request when the encapsulation processing of the request to be encapsulated by the plug-in No. 5 is completed.

The optional implementation mode can selectively utilize the plug-in the requester through presetting calling state information of the second parameter, so that the plug-in is more flexible to use.

Optionally, before step 301, the method may further include: setting a call-free condition of a second parameter for a first plugin in a first plugin set, wherein the call-free condition comprises that a request of current encapsulation processing of the first plugin is the same as a request of previous encapsulation processing, and the interval time of encapsulation processing does not reach a preset threshold; and in the running first plug-in queue in step 302, at least one first plug-in preset for performing packaging processing on a request to be packaged of a target application, and sequentially performing packaging processing on the request to be packaged may include: and responding to the first plugin meeting the call-free condition, if the first plugin is finished running, intercepting a request obtained by the first plugin for packaging, and stopping packaging of the request in a requester.

In this alternative implementation, the execution body may set the call-free condition of the second parameter in advance. And under the condition that the calling-free condition is met, if the execution main body finishes running the first plug-in, the second parameter is not called. The above-mentioned interval time of the encapsulation process may be determined by any point in time during the encapsulation process, such as the start point in time of the encapsulation process, i.e. the point in time when the first card receives the request. In this way, the execution body described above can determine the time interval between the start time point of the encapsulation process of the request of the previous encapsulation process and the start time point of the encapsulation process of the request of the current encapsulation process. For another example, any of the above time points may be a time point when the request package is completed.

The implementation modes can avoid repeated processing of the same request in a short time through calling-free conditions, so that operation resources can be saved, and invalid operation of the plug-in is avoided.

Step 303, a request to be sent is sent to the server.

In this embodiment, the execution body may send the request to be sent, which is obtained by the encapsulation processing, to the server. In particular, the request may be various requests of the application, for example, an update request of the application, or a request related to a web page, such as a request for display data of the web page, or an update request of the web page, or the like.

The plugins in the embodiment are arranged in a queue manner, and the requests to be packaged can be packaged in sequence, so that the processing sequence of the requests to be packaged by different plugins can be accurately controlled.

With further reference to fig. 4, a flow 400 of yet another embodiment of a method for sending a request is shown. The flow 400 of the method for sending a request comprises the steps of:

step 401, obtain a request to be encapsulated generated in a target application.

In this embodiment, an execution body of the method for transmitting a request (for example, the terminal device shown in fig. 1) may acquire a request to be encapsulated. A plurality of applications may be installed on the device, where the request to be encapsulated is generated in a target application of the plurality of applications. The request to be packaged refers to a request to be subjected to packaging processing. The encapsulation processing of the request to be encapsulated herein may refer to combining the data and the functions of the request to be encapsulated to form a whole, and hiding the attribute and implementation details of the data, and only disclosing the interface externally.

Step 402, performing packaging processing before sending a request to be packaged by using a first plugin corresponding to a target application in a preset first plugin set to obtain the request to be sent, wherein the first plugin set is preset in a requester, the requester is preset to perform packaging processing on the request to be packaged generated by the target application, and processing operations executed by each first plugin in the first plugin set on the request to be packaged are different.

In this embodiment, the executing body may perform encapsulation processing on the obtained request to be encapsulated by using the plugins in the first plugin set, so as to process the request to be encapsulated into a request to be sent, so as to send the request to be encapsulated. The plug-ins in the first set of plug-ins may be referred to as first plug-ins, which plug-ins correspond to the target application. The correspondence here refers to that the first plug-in is used to process a request to be encapsulated generated at the target application. It should be noted that, in some cases, the first plug-in may not only perform the encapsulation processing on the request to be encapsulated, but also perform other processing operations.

Step 403, sending a request to be sent to a server.

And step 404, receiving response information for the target application fed back by the server.

In this embodiment, the executing body may receive response information fed back by the server for the target application. After that, the execution body may process the response information in the requester.

And 405, performing pre-utilization processing on the response information by utilizing a second plugin corresponding to the target application in a preset second plugin set, and transmitting a processing result to the target application, wherein the second plugin set is preset in the requester.

In this embodiment, the requester is further configured in advance to perform pre-utilization processing on the response information for the target application. The execution body may perform the pre-utilization processing on the response information by using the plug-ins in the second plug-in set. The plug-ins in the second set of plug-ins may be referred to as second plug-ins. The pre-utilization processing refers to processing of response information before the target application utilizes the response information. In particular, utilizing preprocessing may include parsing and/or format conversion, such as converting response information in other formats into a specified format, such as Json format.

In practice, the encapsulation processing operations performed by each second plug-in the second set of plug-ins for the request to be encapsulated may be different, each of which may perform one or more encapsulation processing operations. For example, one second plug-in may perform the operation of converting the format of the request to be packaged, and the other second plug-in may perform the operation of tagging the request to be packaged with a particular tag.

The embodiment can process the response information by using the plugins in the second plugin set in the requester, can rapidly expand the function related to the response information processing in the requester, and ensures that the coupling degree of the expanded content and each module is lower. The function related to response information processing in the requester can also be flexibly added or deleted by the plug-ins in the second plug-in set.

In some alternative implementations of the present embodiment, the second set of plug-ins may include a second plug-in queue; and in step 405, performing a pre-utilization process on the response information by using a second plug-in corresponding to the target application in the preset second plug-in set may include: and responding to the response information comprising the identification of the target application, and operating at least one second plugin in the second plugin queue, which is preset and used for carrying out utilization pretreatment on the response information of the target application, by calling a designated processing method in a requester corresponding to the identification of the target application, so as to sequentially carry out utilization pretreatment on the response information.

In these alternative implementations, the execution entity may execute at least one second plug-in the second plug-in queue by using a specified processing method, such as handle (), and sequentially perform the pre-utilization processing on the response information. In the requester, not only the plug-in pool corresponding to the first plug-in set but also the plug-in pool corresponding to the second plug-in set may be provided, that is, the second plug-in set is implemented as the plug-in pool. And utilizing the plug-in pool corresponding to the second plug-in set to pre-process the response information. In particular, the cards in the second card queue may be arranged according to various rules, for example, may be arranged according to the time sequence in which the cards are added to the card queue. Further, the placement of some or all of the cards in the second card queue may be developer-specified.

The at least one second plugin may include all plugins in the second plugin queue, so the execution body may make the response information sequentially pass through all second plugins in the second plugin queue according to the arrangement order of the second plugins in the queue. In some cases, the at least one second plugin may include only a part of plugins in the second plugin queue, so the execution body may use only the part of plugins in the second plugin queue to perform the pre-use processing on the response information in sequence according to the arrangement order of the part of plugins in the second plugin queue.

The plugins in the implementation modes are arranged in a queue mode, and response information can be sequentially subjected to pre-utilization processing, so that the processing sequence of different plugins on the response information can be accurately controlled.

Optionally, each card in the second card set includes a first parameter and a second parameter, the first parameter indicates a content to be processed of the card for response information, and the second parameter indicates that, in response to the card being operated, a next card in the at least one second card is operated according to an order of the second card queue.

In this alternative implementation, each plug-in the second set of plug-ins may contain a first parameter, such as options (), and may also contain a second parameter, such as next (). For each plug-in the second set of plug-ins, the first parameter may indicate the content of the plug-in to be processed for the response information. The content to be processed here may be a parameter in the response information. The execution body may sequentially run all the cards in the second card queue to process the request to be encapsulated by using the second parameter in each card.

The implementation modes can accurately and orderly operate each plug-in through the first parameter and the second parameter, and clearly respond to the content to be processed in the information, and process the request to be packaged in a targeted manner.

Optionally, before step 401, the method may further include: setting calling state information of a second parameter for a second plugin in a second plugin set, wherein the calling state information comprises first state information representing that the second parameter is called after the second plugin is operated, or second state information representing that the second parameter is not called after the second plugin is operated; and at least one second plug-in for performing pre-utilization processing on the response information of the target application in the running second plug-in queue, where the pre-utilization processing on the response information sequentially may include: responding to the calling state information of the second parameter of the second plugin as second state information, and if the second plugin is finished running, running the next plugin of the second plugin according to the sequence of the at least one second plugin in the second plugin queue; and responding to the calling state information of the second parameter of the second plug-in as second state information, if the second plug-in is finished running, intercepting the response information obtained by running the second plug-in for utilizing the preprocessing, and stopping the utilization preprocessing of the obtained response information in the requester.

In this alternative implementation, for a second plug-in the second plug-in queue, the execution body may set call state information of a second parameter for the second plug-in. The parameter values herein may include first state information and second state information. Specifically, the first state information may be used to indicate that the second parameter is called after the second plug-in is finished running, and the second state information may be used to indicate that the second parameter is not called after the second plug-in is finished running.

In the case that the call state information is the first state information, the execution body may run all the plugins in the second plugin queue to perform the pre-utilization processing on the response information. After the second plug-in is operated to perform the pre-utilization processing, the next plug-in may be used to perform further pre-utilization processing on the response information after the second plug-in performs the pre-utilization processing. And in the case that the call state information is the second state information, the at least one second plug-in for performing the pre-processing on the response information of the target application may be only a part of plug-ins in the second plug-in queue. Then, the executing body may intercept the request obtained by the second plug-in after the second plug-in finishes running and use the pre-processing response information, and terminate the pre-processing of the request in the requester. In practice, after the pre-use processing is suspended, the executing body may directly use the request obtained by the pre-use processing of the second plugin as the request to be sent, or may recall the processing method specified in the requester, and execute the plugin in the at least one second plugin based on the information indicating the at least one second plugin pre-stored in the requester, and continue to perform the pre-use processing on the response information obtained finally before the suspension.

Optionally, before step 401, the method may further include: setting a call-free condition of a second parameter for a second plugin in a second plugin set, wherein the call-free condition comprises that a request of the second plugin for current encapsulation processing is the same as a request of the previous encapsulation processing, and the interval time of the encapsulation processing does not reach a preset threshold; and at least one second plugin, which is preset in the second plugin queue and is used for performing pre-utilization processing on response information of the target application, sequentially performs pre-utilization processing on the response information, and includes: and if the second plug-in meets the call-free condition, intercepting and operating the response information obtained by the second plug-in for utilizing the preprocessing and stopping the utilizing preprocessing of the response information in the requester.

In this alternative implementation, the execution body may set the call-free condition of the second parameter in advance. And under the condition that the calling-free condition is met, if the execution main body finishes running the second plug-in, the second parameter is not called. The above-mentioned interval time using the preprocessing may be determined by any point in time during the preprocessing, such as the start point in time of the preprocessing, that is, the point in time when the second plug-in receives the response information. In this way, the execution subject can determine the time interval between the start time point of the pre-use processing of the response information of the previous pre-use processing and the start time point of the pre-use processing of the response information of the current pre-use processing. For another example, any of the above-described time points may be a time point when the response information is subjected to preprocessing.

The implementation modes can avoid repeatedly processing the same response information in a short time through calling-free conditions, so that operation resources can be saved, and invalid operation of the plug-in unit is avoided.

In some optional implementations of this embodiment, the method may further include: responding to the detection instruction to add the plug-in to be added of the target application to the second plug-in set, and obtaining the plug-in to be added, wherein the plug-in to be added is a plug-in except for the plug-in the second plug-in set, and the plug-in to be added is a plug-in for performing utilization preprocessing on response information of the target application; adding the plug-in to be added into the second plug-in set by calling a specified adding method in the requester corresponding to the identification of the target application; determining a plug-in to be deleted according to the instruction of the plug-in to be deleted, which indicates the target application, from the second plug-in set, wherein the plug-in to be deleted is a plug-in the second plug-in set, and the plug-in to be added is a plug-in for performing utilization preprocessing on response information of the target application; and deleting the plug-in to be deleted from the second plug-in set by calling a specified deletion method in the requester corresponding to the identification of the target application.

In these alternative implementations, the execution body may adjust the plugins in the second plugin set by invoking methods in various application interfaces. For example, if a locally generated or other instruction sent by the electronic device to instruct to add the plug-in to be added is detected, the execution body may call a preset method, such as use (), to add the plug-in to be added to the second plug-in set. In addition, if a command indicating to delete the plug-in to be deleted, which is generated locally or sent by other electronic devices, is detected, the execution body may call a preset method, such as an abart (), and delete the plug-in to be deleted from the second plug-in set.

With continued reference to fig. 5, fig. 5 is a flowchart of a method for sending a request according to the present embodiment. In fig. 5, the executing body may acquire the request to be encapsulated, and call a preset method to process the request to be encapsulated, so as to obtain a preliminary processing request. The preset method may include REST method, and may further include some packaged custom methods. The executing entity may then request the preliminary processing by requesting a plug-in pool. The request plug-in pool corresponds to the first plug-in set, the execution body can operate each first plug-in cascaded in the request plug-in pool, and package the preliminary processing requests sequentially to obtain packaged requests. And then, the execution body can send a packaged request by utilizing the AJAX module and receive response information fed back by the server. The executing entity may then pass the response information through the response plug-in pool. The response plug-in pool corresponds to the second plug-in set, and the execution main body can operate each second plug-in cascaded in the response plug-in pool, and sequentially perform utilization pretreatment on response information and obtain a response result. The processing performed by each of the cards in cascade means that the processing result outputted from the card in the previous stage is inputted to the card in the next stage to continue the processing.

These alternative implementations may flexibly adjust the plug-ins in the requester to enable more accurate pre-utilization processing of the response information.

With further reference to fig. 6, as an implementation of the method shown in the above figures, the present application provides an embodiment of an apparatus for sending a request, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 2, and the embodiment of the apparatus may further include the same or corresponding features or effects as the embodiment of the method shown in fig. 2, 3, and 4, except for the features described below. The device can be applied to various electronic equipment.

As shown in fig. 6, the apparatus 600 for transmitting a request of the present embodiment includes: an acquisition unit 601, an encapsulation unit 602, and a transmission unit 603. Wherein, the acquiring unit 601 is configured to acquire a request to be packaged generated in a target application; the packaging unit 602 is configured to perform packaging processing before sending a request to be packaged by using a first plugin corresponding to a target application in a preset first plugin set to obtain the request to be sent, where the first plugin set is preset in a requester, and the requester is configured in advance to perform packaging processing on the request to be packaged generated by the target application; the transmitting unit 603 is configured to transmit a request to be transmitted to the server.

In some embodiments, the obtaining unit 601 of the apparatus 600 for sending a request may obtain a request to be encapsulated. The device may be installed with a plurality of applications, where the request to be encapsulated is generated in a target application of the plurality of applications. The request to be packaged refers to a request to be subjected to packaging processing.

In some embodiments, the encapsulation unit 602 may perform encapsulation processing on the acquired request to be encapsulated by using the plugins in the first plugin set, so as to process the request to be encapsulated into a request to be sent, so as to facilitate sending. The plug-ins in the first set of plug-ins may be referred to as first plug-ins, which plug-ins correspond to the target application.

In some embodiments, the sending unit 603 may send the request to be sent, which is obtained by the encapsulation processing described above, to the server. In particular, the request herein may be various requests related to the application, for example, an update request of the application, or a request related to the page, such as a request for display data of the page, or an update request of the page, or the like.

In some alternative implementations of the present embodiment, the first set of plugins includes a first plugin queue; and a packaging unit configured to perform packaging processing before sending the request to be packaged by using a first plug-in corresponding to the target application in the preset first plug-in set in the following manner: and responding to the request to be packaged, wherein the request to be packaged comprises the identification of the target application, and operating at least one first plugin which is preset and is used for packaging the request to be packaged of the target application in the first plugin queue by calling a designated processing device in a requester corresponding to the identification of the target application.

In some optional implementations of this embodiment, the apparatus further includes: the first setting unit is configured to set calling state information of a second parameter for a first plugin in the first plugin set, wherein the calling state information comprises first state information representing that the second parameter is called after the first plugin is operated, or second state information representing that the second parameter is not called after the first plugin is operated; and the packaging unit is further configured to execute at least one first plug-in which is preset and is used for packaging the request to be packaged of the target application in the first plug-in queue, and sequentially perform packaging processing on the request to be packaged: responding to the calling state information of the second parameter of the first plugin as first state information, and if the first plugin is finished running, running the next plugin of the first plugin according to the sequence of the at least one first plugin in the first plugin queue; and responding to the calling state information of the second parameter of the first plugin as second state information, if the first plugin is finished running, intercepting a request obtained by running the first plugin for packaging processing, and stopping packaging processing of the request in a requester.

In some optional implementations of this embodiment, the apparatus further includes: the second setting unit is configured to set a call-free condition of a second parameter for a first plugin in the first plugin set, wherein the call-free condition comprises that a request of current encapsulation processing of the first plugin is the same as a request of previous encapsulation processing, and the interval time of encapsulation processing does not reach a preset threshold; and the packaging unit is further configured to execute at least one first plug-in which is preset and is used for packaging the request to be packaged of the target application in the first plug-in queue, and sequentially perform packaging processing on the request to be packaged: and responding to the first plugin meeting the call-free condition, if the first plugin is finished running, intercepting a request obtained by the first plugin for packaging, and stopping packaging of the request in a requester.

In some optional implementations of this embodiment, the apparatus further includes: the first adding unit is configured to respond to the detection of an instruction for indicating to add the plug-in to be added of the target application into the first plug-in set, and obtain the plug-in to be added, wherein the plug-in to be added is a plug-in except for the plug-in the first plug-in set, and the plug-in to be added is a plug-in for packaging processing of a request to be packaged of the target application; adding the plug-in to be added into the first plug-in set by calling a designated adding device in a requester corresponding to the identification of the target application; the first deleting unit is configured to respond to the detection of an instruction for deleting the plug-in to be deleted of the target application from the first plug-in set, and the plug-in to be deleted is a plug-in the first plug-in set and is a plug-in for packaging a request to be packaged of the target application; and deleting the plug-in to be deleted from the first plug-in set by calling a designated deleting device in the requester corresponding to the identification of the target application.

In some optional implementations of this embodiment, the requestor is further preconfigured to pre-utilize the response information for the target application, the apparatus further comprising: the receiving unit is configured to receive response information, fed back by the server, of the target application; and the pre-processing unit is configured to perform pre-processing on the response information by using a second plugin corresponding to the target application in a preset second plugin set, and transmit a processing result to the target application, wherein the second plugin set is preset in the requester.

In some alternative implementations of the present embodiment, the second set of plugins includes a second plugin queue; and a pre-utilization processing unit, further configured to perform pre-utilization processing on the response information by using a second plug-in corresponding to the target application in the preset second plug-in set in the following manner: and responding to the response information comprising the identification of the target application, and operating at least one second plugin in the second plugin queue, which is preset and used for carrying out utilization pretreatment on the response information of the target application, by calling a designated processing device in a requester corresponding to the identification of the target application, so as to sequentially carry out utilization pretreatment on the response information.

In some optional implementations of this embodiment, the second plugin in the second plugin set includes a first parameter and a second parameter, the second parameter indicating content of the second plugin to be processed of the response information, the second parameter indicating that, in response to completion of the second plugin operation, a next plugin of the at least one second plugin is operated in an order of the at least one second plugin in the second plugin queue.

In some optional implementations of this embodiment, the apparatus further includes: the third setting unit is configured to set calling state information of a second parameter for a second plugin in the second plugin set, wherein the calling state information comprises first state information representing that the second parameter is called after the second plugin is operated, or second state information representing that the second parameter is not called after the second plugin is operated; and a pre-utilization processing unit, further configured to execute at least one second plug-in preset for performing pre-utilization processing on response information of the target application in the second plug-in queue, and sequentially perform pre-utilization processing on the response information: responding to the calling state information of the second parameter of the second plugin as second state information, and if the second plugin is finished running, running the next plugin of the second plugin according to the sequence of the at least one second plugin in the second plugin queue; and responding to the calling state information of the second parameter of the second plug-in as second state information, if the second plug-in is finished running, intercepting the response information obtained by running the second plug-in for utilizing the preprocessing, and stopping the utilizing preprocessing of the response information in the requester.

In some optional implementations of this embodiment, the apparatus further includes: a fourth setting unit, configured to set a call-free condition of a second parameter for a second plugin in the second plugin set, where the call-free condition includes that a request of a current package process of the second plugin is the same as a request of a previous package process, and an interval time of the package process does not reach a preset threshold; and a pre-utilization processing unit, further configured to execute at least one second plug-in preset for performing pre-utilization processing on response information of the target application in the second plug-in queue, and sequentially perform pre-utilization processing on the response information: and if the second plug-in meets the call-free condition, intercepting and operating the response information obtained by the second plug-in for utilizing the preprocessing and stopping the utilizing preprocessing of the response information in the requester.

In some optional implementations of this embodiment, the apparatus further includes: the second adding unit is configured to respond to the detection of an instruction for indicating to add the plug-in to be added of the target application into the second plug-in set, and obtain the plug-in to be added, wherein the plug-in to be added is a plug-in except for the plug-in the second plug-in set, and the plug-in to be added is a plug-in for performing utilization preprocessing on response information of the target application; adding the plug-in to be added into the second plug-in set by calling a specified adding method in the requester corresponding to the identification of the target application; the second deleting unit is configured to respond to the detection of an instruction for deleting the plug-in to be deleted of the target application from the second plug-in set, and the plug-in to be deleted is a plug-in the second plug-in set and is a plug-in for performing utilization preprocessing on response information of the target application; and deleting the plug-in to be deleted from the second plug-in set by calling a specified deletion method in the requester corresponding to the identification of the target application.

As shown in fig. 7, the electronic device 700 may include a processing means (e.g., a central processor, a graphics processor, etc.) 701, which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 702 or a program loaded from a storage means 708 into a Random Access Memory (RAM) 703. In the RAM703, various programs and data required for the operation of the electronic device 700 are also stored. The processing device 701, the ROM 702, and the RAM703 are connected to each other through a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.

In general, the following devices may be connected to the I/O interface 705: input devices 706 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, and the like; an output device 707 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 708 including, for example, magnetic tape, hard disk, etc.; and a communication device 709. The communication means 709 may allow the electronic device 700 to communicate wirelessly or by wire with other devices to exchange data. While fig. 7 shows an electronic device 700 having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead. Each block shown in fig. 7 may represent one device or a plurality of devices as needed.

In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via communication device 709, or installed from storage 708, or installed from ROM 702. The above-described functions defined in the methods of the embodiments of the present disclosure are performed when the computer program is executed by the processing device 701. It should be noted that the computer readable medium of the embodiments of the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In an embodiment of the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. Whereas in embodiments of the present disclosure, the computer-readable signal medium may comprise a data signal propagated in baseband or as part of a carrier wave, with computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units involved in the embodiments of the present application may be implemented in software or in hardware. The described units may also be provided in a processor, for example, described as: a processor includes an acquisition unit, an encapsulation unit, and a transmission unit. The names of these units do not in some cases limit the unit itself, and the acquisition unit may also be described as "a unit that acquires a request to be encapsulated generated in a target application", for example.

As another aspect, the present application also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the apparatus to: acquiring a request to be packaged generated in a target application; the method comprises the steps that a first plugin corresponding to a target application in a preset first plugin set is utilized to perform packaging processing before sending a request to be packaged to obtain the request to be sent, wherein the first plugin set is preset in a requester, and the requester is preset to perform packaging processing on the request to be packaged generated by the target application; and sending a request to be sent to a server.

The above description is only illustrative of the preferred embodiments of the present application and of the principles of the technology employed. It will be appreciated by persons skilled in the art that the scope of the application referred to in the present application is not limited to the specific combinations of the technical features described above, but also covers other technical features formed by any combination of the technical features described above or their equivalents without departing from the inventive concept described above. Such as the above-mentioned features and the technical features disclosed in the present application (but not limited to) having similar functions are replaced with each other.

Claims

1. A method for sending a request, the method comprising:

acquiring a request to be packaged generated in a target application;

the method comprises the steps that a first plugin corresponding to a target application in a preset first plugin set is utilized to perform packaging processing before sending on a request to be packaged to obtain the request to be sent, wherein the first plugin set is preset in a requester, and the requester is preset to perform packaging processing on the request to be packaged generated by the target application;

the request to be sent is sent to a server;

wherein the first set of plugins includes a first plugin queue; and

the packaging process before sending the request to be packaged by using a first plugin corresponding to the target application in the preset first plugin set includes:

responding to the request to be packaged, wherein the request to be packaged comprises the identification of the target application, and operating at least one first plugin which is preset and is used for carrying out the packaging processing on the request to be packaged of the target application in the first plugin queue by calling a designated processing method in a requester corresponding to the identification of the target application;

The first plugin in the first plugin set comprises a first parameter and a second parameter, wherein the first parameter of the first plugin indicates the to-be-processed content of a request to be packaged of the first plugin, and the second parameter of the first plugin indicates that the next plugin of the first plugin in the at least one first plugin sequence in the first plugin queue according to the sequence of the at least one first plugin after the first plugin finishes;

wherein the method further comprises:

setting calling state information of a second parameter of the first plugin for a first plugin in the first plugin set, wherein the calling state information comprises first state information representing that the second parameter of the first plugin is called after the first plugin is operated, or second state information representing that the second parameter of the first plugin is not called after the first plugin is operated; and

the running the at least one first plugin, which is preset and used for performing the encapsulation processing on the request to be encapsulated of the target application, sequentially performs the encapsulation processing on the request to be encapsulated, including:

responding to the calling state information of the second parameter of the first plugin as first state information, and if the first plugin is finished running, running the next plugin of the first plugin in the at least one first plugin according to the sequence of the at least one first plugin in the first plugin queue;

And responding to the calling state information of the second parameter of the first plugin as second state information, intercepting a request obtained by the encapsulation processing of the first plugin when the first plugin is operated, and stopping the encapsulation processing of the request in the requester.

2. The method of claim 1, wherein the method further comprises:

setting a call-free condition of a second parameter of the first plugin for a first plugin in the first plugin set, wherein the call-free condition comprises that a request of current encapsulation processing of the first plugin is the same as a request of previous encapsulation processing, and the interval time of encapsulation processing does not reach a preset threshold; and

and responding to the first plugin to meet the call-free condition, if the first plugin is finished running, intercepting a request obtained by the first plugin for packaging processing, and stopping packaging processing of the request in the requester.

3. The method according to one of claims 1-2, wherein the method further comprises:

responding to a detection instruction for adding a plug-in to be added of the target application into the first plug-in set, and obtaining the plug-in to be added, wherein the plug-in to be added is a plug-in except for the plug-ins in the first plug-in set, and the plug-in to be added is a plug-in for packaging a request to be packaged of the target application; adding the plug-in to be added to the first plug-in set by calling a specified adding method in a requester corresponding to the identification of the target application;

determining a plug-in to be deleted of the target application in response to detecting an instruction for indicating the plug-in to be deleted from the first plug-in set, wherein the plug-in to be deleted is a plug-in the first plug-in set, and the plug-in to be added is a plug-in for performing encapsulation processing on a request to be encapsulated of the target application; and deleting the plug-in to be deleted from the first plug-in set by calling a specified deleting method in the requester corresponding to the identification of the target application.

4. The method of claim 1, wherein the requestor is further preconfigured to pre-utilize response information for the target application, the method further comprising:

receiving response information, fed back by the server, aiming at the target application;

and utilizing a second plugin corresponding to the target application in a preset second plugin set to perform pre-utilization processing on the response information and transmitting a processing result to the target application, wherein the second plugin set is preset in the requester.

5. The method of claim 4, wherein the second set of plugins comprises a second plugin queue; and

the utilizing the second plugin corresponding to the target application in the preset second plugin set to conduct utilizing pretreatment on the response information comprises the following steps:

and responding to the response information comprising the identification of the target application, and operating at least one second plugin which is preset and is used for carrying out the pre-utilization processing on the response information of the target application in the second plugin queue by calling a designated processing method in a requester corresponding to the identification of the target application, wherein the at least one second plugin is used for carrying out the pre-utilization processing on the response information in sequence.

6. The method of claim 5, wherein a second plug-in the second set of plug-ins includes a first parameter and a second parameter, the first parameter of the second plug-in indicating content to be processed of the second plug-in to response information, the second parameter of the second plug-in indicating that a next plug-in of the at least one second plug-in is operated in the order of the at least one second plug-in the second plug-in queue in response to the second plug-in being operated.

7. The method of claim 5, wherein the method further comprises:

setting calling state information of a second parameter of the second plugin for the second plugin in the second plugin set, wherein the calling state information comprises first state information representing that the second parameter of the second plugin is called after the second plugin is operated, or second state information representing that the second parameter of the second plugin is not called after the second plugin is operated; and

and running at least one second plugin, which is preset and used for carrying out the pre-utilization processing on the response information of the target application, in the second plugin queue, and sequentially carrying out the pre-utilization processing on the response information, wherein the pre-utilization processing comprises the following steps:

Responding to the calling state information of the second parameter of the second plugin as second state information, and if the second plugin is finished running, running the next plugin of the second plugin in the at least one second plugin according to the sequence of the at least one second plugin in the second plugin queue;

and responding to the calling state information of the second parameter of the second plug-in as second state information, if the second plug-in is finished running, intercepting response information obtained by running the second plug-in for utilizing the preprocessing, and stopping the utilizing preprocessing of the response information in the requester.

8. The method of claim 5, wherein the method further comprises:

setting a call-free condition of a second parameter of the second plugin for the second plugin in the second plugin set, wherein the call-free condition comprises that a request of current encapsulation processing of the second plugin is the same as a request of previous encapsulation processing, and the interval time of encapsulation processing does not reach a preset threshold; and

And responding to the second plugin to meet the call-free condition, if the second plugin is finished running, intercepting and running response information obtained by the second plugin for utilizing pretreatment, and stopping the utilization pretreatment of the response information in the requester.

9. The method according to one of claims 4-8, wherein the method further comprises:

responding to the detection of an instruction for indicating to add the plug-in to be added of the target application to the second plug-in set, and obtaining the plug-in to be added, wherein the plug-in to be added is a plug-in except for the plug-in the second plug-in set, and the plug-in to be added is a plug-in for performing the pre-utilization processing on response information of the target application; adding the plug-in to be added to the second plug-in set by calling a specified adding method in a requester corresponding to the identification of the target application;

determining a plug-in to be deleted according to the detection instruction of the plug-in to be deleted of the target application from the second plug-in set, wherein the plug-in to be deleted is a plug-in the second plug-in set, and the plug-in to be added is a plug-in for performing the pre-utilization processing on response information of the target application; and deleting the plug-in to be deleted from the second plug-in set by calling a specified deleting method in the requester corresponding to the identification of the target application.

10. A requesting apparatus for application to a terminal device, the apparatus comprising:

an acquisition unit configured to acquire a request to be packaged generated in a target application;

the packaging unit is configured to utilize a first plugin corresponding to the target application in a preset first plugin set to perform packaging processing before sending the request to be packaged to obtain the request to be sent, wherein the first plugin set is preset in a requester, and the requester is configured to perform packaging processing on the request to be packaged generated by the target application in advance;

a transmitting unit configured to transmit the request to be transmitted to a server;

wherein the first set of plugins includes a first plugin queue; and

the packaging unit is further configured to execute the packaging process before sending the request to be packaged by using a first plug-in corresponding to the target application in the preset first plug-in set in the following manner:

responding to the request to be packaged, wherein the request to be packaged comprises the identification of the target application, and operating at least one first plugin which is preset and is used for carrying out the packaging processing on the request to be packaged of the target application in the first plugin queue by calling a designated processing device in a requester corresponding to the identification of the target application;

wherein the apparatus further comprises:

the first setting unit is configured to set calling state information of second parameters of the first plugin for the first plugin in the first plugin set, wherein the calling state information comprises first state information representing that the second parameters of the first plugin are called after the first plugin is operated, or second state information representing that the second parameters of the first plugin are not called after the first plugin is operated; and

the packaging unit is further configured to execute at least one first plugin preset for performing the packaging process on the request to be packaged of the target application in the first plugin queue according to the following manner, and sequentially perform the packaging process on the request to be packaged:

11. The apparatus of claim 10, wherein the apparatus further comprises:

a second setting unit, configured to set, for a first plugin in the first plugin set, a call-free condition of a second parameter of the first plugin, where the call-free condition includes that a request of a current package process of the first plugin is the same as a request of a previous package process, and an interval time of the package process does not reach a preset threshold; and

12. The apparatus according to one of claims 10-11, wherein the apparatus further comprises:

the first adding unit is configured to respond to the detection of an instruction for indicating to add the plug-in to be added of the target application to the first plug-in set, and acquire the plug-in to be added, wherein the plug-in to be added is a plug-in except for the plug-in the first plug-in set, and the plug-in to be added is a plug-in for carrying out encapsulation processing on a request to be encapsulated of the target application; adding the plug-in to be added to the first plug-in set by calling a designated adding device in a requester corresponding to the identification of the target application;

a first deleting unit configured to determine, in response to detecting an instruction indicating that a plug-in to be deleted of the target application is from the first plug-in set, the plug-in to be deleted is a plug-in the first plug-in set, and the plug-in to be added is a plug-in for performing encapsulation processing on a request to be encapsulated of the target application; and deleting the plug-in to be deleted from the first plug-in set by calling a designated deleting device in a requester corresponding to the identification of the target application.

13. An electronic device, comprising:

one or more processors;

storage means for storing one or more programs,

when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-9.

14. A computer readable storage medium having stored thereon a computer program, wherein the program when executed by a processor implements the method of any of claims 1-9.