CN113553206A - Data event execution method and device, electronic equipment and computer readable medium - Google Patents
Data event execution method and device, electronic equipment and computer readable medium Download PDFInfo
- Publication number
- CN113553206A CN113553206A CN202111104631.4A CN202111104631A CN113553206A CN 113553206 A CN113553206 A CN 113553206A CN 202111104631 A CN202111104631 A CN 202111104631A CN 113553206 A CN113553206 A CN 113553206A
- Authority
- CN
- China
- Prior art keywords
- data
- data event
- event
- execution
- list
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
- G06F9/548—Object oriented; Remote method invocation [RMI]
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the disclosure discloses a data event execution method, a data event execution device, an electronic device and a computer readable medium. One embodiment of the method comprises: responding to the monitoring of the starting of the user side, and acquiring a data event list; in response to receiving data event request information, matching the data event request information with the data event list to obtain a matching result; updating a message queue based on the data event request information in response to determining that the matching result meets a preset condition; and performing data event execution operation on the message corresponding to the data event request information in the message queue according to a data execution module in a preset data execution module list. This embodiment may improve the efficiency of data event execution.
Description
Technical Field
Embodiments of the present disclosure relate to the field of computer technologies, and in particular, to a data event execution method, apparatus, electronic device, and computer-readable medium.
Background
The data event executing method is one technology for processing user side request. At present, when a data event is executed, the following method is generally adopted: and setting an interface calling function at the user side for remotely calling a plurality of server-side interfaces so as to process the request of the user side. Thereby, the data event execution operation is completed.
However, when performing data event execution in the above manner, there are often technical problems as follows:
when any one of the plurality of server interfaces changes, the server call function set in the client needs to be adjusted in time to continue the data event execution operation, and meanwhile, when the service requirement (for example, the function of adding the data event execution result sending function) changes, the client service logic needs to be actively modified to continue the data event request operation. Therefore, the coupling between the client and the server is high, which results in a decrease in the efficiency of executing data events.
Disclosure of Invention
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
Some embodiments of the present disclosure propose data event execution methods, apparatuses, electronic devices and computer readable media to solve the technical problems mentioned in the background section above.
In a first aspect, some embodiments of the present disclosure provide a data event execution method, including: responding to the monitoring of the starting of the user side, and acquiring a data event list; in response to receiving data event request information, matching the data event request information with the data event list to obtain a matching result; updating a message queue based on the data event request information in response to determining that the matching result meets a preset condition; and performing data event execution operation on the message corresponding to the data event request information in the message queue according to a data execution module in a preset data execution module list.
In a second aspect, some embodiments of the present disclosure provide a data event execution apparatus, including: the acquisition unit is configured to respond to the monitoring of the starting of the user terminal and acquire a data event list; the matching unit is configured to respond to the received data event request information, match the data event request information with the data event list and obtain a matching result; an updating unit configured to update a message queue based on the data event request information in response to determining that the matching result satisfies a preset condition; and the data event execution unit is configured to perform data event execution operation on the message corresponding to the data event request information in the message queue according to a data execution module in a preset data execution module list.
In a third aspect, some embodiments of the present disclosure provide an electronic device, comprising: one or more processors; a storage device having one or more programs stored thereon, which when executed by one or more processors, cause the one or more processors to implement the method described in any of the implementations of the first aspect.
In a fourth aspect, some embodiments of the present disclosure provide a computer readable medium on which a computer program is stored, wherein the program, when executed by a processor, implements the method described in any of the implementations of the first aspect.
The above embodiments of the present disclosure have the following advantages: by the data event execution method of some embodiments of the present disclosure, the efficiency of data event execution can be improved. Specifically, the reason for the reduced efficiency of executing the data event is that: when any one of the plurality of server interfaces changes, the server call function set in the client needs to be adjusted in time to continue the data event execution operation, and meanwhile, when the service requirement (for example, the function of adding the data event execution result sending function) changes, the client service logic needs to be actively modified to continue the data event request operation. Therefore, the coupling degree between the client and the server is higher. Based on this, the data event execution method of some embodiments of the present disclosure first obtains the data event list in response to monitoring the start of the user side. By introducing a data event list, it can be used to characterize a plurality of available server interfaces. And then, responding to the received data event request information, and matching the data event request information with the data event list to obtain a matching result. By matching it can be determined whether a server interface exists for performing the data event request information. And then, in response to the fact that the matching result meets the preset condition, updating the message queue based on the data event request information. The message queue is introduced to serve as a container for data event requests between the client and the server, so that direct communication between the client and the client is avoided. Therefore, decoupling between the user side and the server side is achieved. And finally, performing data event execution operation on the message corresponding to the data event request information in the message queue according to a data execution module in a preset data execution module list. Therefore, the data event execution operation can be completed on the premise of realizing decoupling between the user side and the server side, and the situation that when any one of a plurality of server side interfaces is changed, the execution of the data event can be continued only after the server side calling function set in the user side needs to be adjusted is avoided. And when the request of the user terminal changes, the function needs to be called again through the interface, and the condition that the server-side interface is called to process the request of the user terminal occurs. Furthermore, the efficiency of data event execution is improved.
Drawings
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and elements are not necessarily drawn to scale.
FIG. 1 is a schematic diagram of one application scenario of a data event execution method of some embodiments of the present disclosure;
FIG. 2 is a flow diagram of some embodiments of a data event execution method according to the present disclosure;
FIG. 3 is a flow diagram of further embodiments of a data event execution method according to the present disclosure;
FIG. 4 is a schematic block diagram of some embodiments of a data event execution apparatus according to the present disclosure;
FIG. 5 is a schematic structural diagram of an electronic device suitable for use in implementing some embodiments of the present disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings. The embodiments and features of the embodiments in the present disclosure may be combined with each other without conflict.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Fig. 1 is a schematic diagram of one application scenario of a data event execution method of some embodiments of the present disclosure.
In the application scenario of fig. 1, first, the computing device 101 may obtain the data event list 103 in response to listening to the start of the user terminal 102. Next, in response to receiving the data event request information 104, the computing device 101 may match the data event request information 104 with the data event list 103 to obtain a matching result 105. Then, the computing device 101 may update the message queue 106 based on the data event request information 104 in response to determining that the matching result 105 satisfies a preset condition. Finally, the computing device 101 may perform a data event execution operation on the message corresponding to the data event request information 104 in the message queue 106 according to a data execution module in a preset data execution module list 107.
The computing device 101 may be hardware or software. When the computing device is hardware, it may be implemented as a distributed cluster composed of multiple servers or terminal devices, or may be implemented as a single server or a single terminal device. When the computing device is embodied as software, it may be installed in the hardware devices enumerated above. It may be implemented, for example, as multiple software or software modules to provide distributed services, or as a single software or software module. And is not particularly limited herein.
It should be understood that the number of computing devices in FIG. 1 is merely illustrative. There may be any number of computing devices, as implementation needs dictate.
With continued reference to fig. 2, a flow 200 of some embodiments of a data event execution method according to the present disclosure is shown. The flow 200 of the data event execution method includes the following steps:
In some embodiments, an executing agent of the data event execution method (e.g., the computing device 101 shown in fig. 1) may obtain the data event list in a wired manner or in a wireless manner in response to listening to the user-side initiation. The user side starting may be that the user starts the user side, or that the user starts a target application (for example, an application such as a shopping mall and a browser) through the user side. Each data event in the data event list may represent an application program interface configured by the server for the started target application.
In some embodiments, the execution subject may match the data event request information with the data event list in response to receiving the data event request information, and obtain a matching result. The data event request message may be a message sent by a user through a user terminal when the user uses the target application. The data event request information may include an application program interface identifier and request information (e.g., request to obtain information about an item, request to obtain information about a web page in a browser, or request to obtain information about an order, etc.). The data event request information may be used to obtain content requested by the request information from an application program interface corresponding to the application program interface identifier, or may be used to obtain order information or article information corresponding to the request information through a service module corresponding to the application program interface identifier. The matching may be determining whether there is a data event characterizing the same application program interface as the application program interface identification. The matching result may be "match" or "no match". A "match" may be used to characterize the presence of a data event in the data event list corresponding to the data event request information described above. The "mismatch" may be used to characterize that no data event corresponding to the data event request information exists in the data event list.
And step 203, responding to the matching result meeting the preset condition, and updating the message queue based on the data event request information.
In some embodiments, the execution agent may update the message queue based on the data event request information in response to determining that the matching result satisfies a preset condition. The preset condition may be that the matching result is "match". Updating the message queue may be adding the data event request information described above as a message to the message queue. In addition, when the queue is updated, a queue message number corresponding to the data event request information can be generated and used for selecting messages from the message queue.
And step 204, performing data event execution operation on the message corresponding to the data event request information in the message queue according to the data execution module in the preset data execution module list.
In some embodiments, the execution main body may perform a data event execution operation on a message corresponding to the data event request information in the message queue according to a data execution module in a preset data execution module list. Each data execution module in the data execution module list may be an application program for performing data event execution operation, or may also be understood as a server for performing data event execution operation. The data event request information may correspond to the messages in the message queue through the queue message number. In practice, the message corresponding to the data event request information in the message queue may be sent to a target data execution module for performing a data event execution operation. The target data execution module may be a data execution module corresponding to the data event matched with the data event request information when the data event request information is matched with the data event list. The corresponding relationship between the data event and the data execution module can be determined through the application program interface represented by the data event in the data event list or the application program interface corresponding to the application program interface identifier included in the data event request information. In practice, the preset data execution module list may also be used to characterize the service processing server cluster. In addition, when the message exists in the message queue, the data event execution operation can be carried out. Therefore, after the message queue is updated, the message corresponding to the data event request information can be determined from the message queue, so that the data event execution operation can be performed.
In some optional implementation manners of some embodiments, before the matching the data event request information with the data event list to obtain a matching result, the executing main body may further include the following steps:
the method comprises the steps of responding to the acquired data event list, updating a local event list by using the data event list, and acquiring an updated event list. The local event list may be an event list stored at the user side before the data event list is acquired. Consider the case where there is a change in the application program interface. Therefore, the local event list can be updated when the data event list is acquired.
And secondly, storing the updated event list to a local cache. By storing the updated event list in a local cache, the data events do not need to be acquired again after the user terminal is started until the user terminal is started next time, and each local event in the local event list can be ensured to represent an available application program interface. Therefore, the data event execution operation can be normally performed without adjusting the server call function (for example, using RestTemplate (remote call service) in the client code) set in the client in time according to the change of the application program interface. Furthermore, the efficiency of data event execution is improved.
The above embodiments of the present disclosure have the following advantages: by the data event execution method of some embodiments of the present disclosure, the efficiency of data event execution can be improved. Specifically, the reason for the reduced efficiency of executing the data event is that: when any one of the plurality of server interfaces changes, the server call function set in the client needs to be adjusted in time to continue the data event execution operation, and meanwhile, when the service requirement (for example, the function of adding the data event execution result sending function) changes, the client service logic needs to be actively modified to continue the data event request operation. Therefore, the coupling degree between the client and the server is higher. Based on this, the data event execution method of some embodiments of the present disclosure first obtains the data event list in response to monitoring the start of the user side. By introducing a data event list, it can be used to characterize a plurality of available server interfaces. And then, responding to the received data event request information, and matching the data event request information with the data event list to obtain a matching result. By matching it can be determined whether a server interface exists for performing the data event request information. And then, in response to the fact that the matching result meets the preset condition, updating the message queue based on the data event request information. The message queue is introduced to serve as a container for data event requests between the client and the server, so that direct communication between the client and the client is avoided. Therefore, decoupling between the user side and the server side is achieved. And finally, performing data event execution operation on the message corresponding to the data event request information in the message queue according to a data execution module in a preset data execution module list. Therefore, the data event execution operation can be completed on the premise of realizing decoupling between the user side and the server side, and the situation that when any one of a plurality of server side interfaces is changed, the execution of the data event can be continued only after the server side calling function set in the user side needs to be adjusted is avoided. And when the request of the user terminal changes, the function needs to be called again through the interface, and the condition that the server-side interface is called to process the request of the user terminal occurs. Furthermore, the efficiency of data event execution is improved.
With further reference to FIG. 3, a flow 300 of further embodiments of a data event execution method is illustrated. The flow 300 of the data event execution method includes the following steps:
In some embodiments, an executing agent of the data event execution method (e.g., computing device 101 shown in FIG. 1) may obtain the list of data events by:
the first step, in response to the monitoring of the starting of the user side, the server side application program interface adapted to each user side is obtained, and a server side application program interface group is obtained. Each server-side application program interface can correspond to an application program interface network address. Each server application program interface in the server application program interface group may be each application program interface in the server at the current time that can perform data event execution operation. Specifically, the service application program interface and the service application program corresponding to the service application program interface may be configured, that is, the conditions required by the service requirement change (for example, adding the data event execution result sending function) are satisfied.
And secondly, performing relational mapping on each server application program interface in the server application program interface group to generate a data event, so as to obtain a data event list. The relational mapping may be to determine an application program interface network address corresponding to the server application program interface as a data event to characterize the server application program interface that can be called.
In practice, there is no real-time update due to the server application program interface adapted for the client. Therefore, it is only necessary to obtain the latest server application program interface adapted to the user side to generate the data event list each time the user side starts (or the user starts the target application program in the user side), so as to ensure that the data event execution operation can be completed. Therefore, the situation that the execution operation of the data event cannot be finished and the execution efficiency of the data event is reduced due to the fact that the data list is not updated timely is avoided. Or the data list is updated too frequently, which occupies more computing resources and storage resources, resulting in a reduction in the execution efficiency of the data event execution operation.
In some embodiments, the execution subject may match the data event request information with the data event list in response to receiving the data event request information, and obtain a matching result. The data event request information may include an event request address. The event request address may be used to characterize the address of the network service requested by the data event request information. The data events in the data event list may include executable network addresses, i.e., the application program interface network addresses. The executable network address may refer to a network address configured by the server for the launched target application. The matching can be performed by:
and matching the event request address in the data event request information with each executable network address in the data event list. The matching result may be "match" or "no match". Wherein the matching may be characterized by the event request address being the same as at least one executable network address in the data event list. A mismatch may be characterized by the event request address not being the same as each executable network address in the data event list.
In practice, it can be determined whether the service list application program interface required for processing the business requirement represented by the data event request information exists or not through matching. If the data event request information exists, the data event request information can be used for carrying out data event execution operation. If the data event request information does not exist, the data event request information can not be used for executing the data event execution operation. Therefore, the condition that the service logic of the user side is adjusted according to the service change can be avoided.
In some embodiments, the executing entity may update the message queue in response to determining that the matching result satisfies a preset condition, by:
first, in response to determining that the data event request information matches the data event list, determining a data event name, a data event service address, and data event execution policy information of the data event request information. The data event name, the data event service address and the data event execution policy information of the data event request information can be acquired from the user side. The data event service address may be a network address for processing the data event request message. The data event execution policy information may include a data event execution number. The data event execution number may be used to characterize an execution sequence of the executable network address included in the at least one data event matching the data event request information in performing the data event execution operation.
And configuring an event request address, the data event name, the data event service address and the data event execution policy information included in the data event request information as a to-be-executed data event, and adding the to-be-executed data event to the message queue. The configuration may be to assemble an event request address included in the data event request information, the data event name, the data event service address, and the data event execution policy information into a data event request packet, which is used as a to-be-executed data event. The adding may be adding the data event request packet corresponding to the data event to be executed as a message file to a message queue, and generating an index file corresponding to the message file.
In some embodiments, the execution subject may select a data execution module matched with the data event to be executed from the preset data execution module list as a matching data module, so as to obtain a matching data module list. The name of the data service included in the matching data module list is the same as the name of the data event included in the data event to be executed. The data execution module in the data execution module list may include a data service name and a data execution network address. The list of matching data modules may be obtained by:
the method comprises the steps of firstly, determining an executable network address included by a data event corresponding to the data event to be executed in the data event list, and obtaining an executable network address group.
And secondly, determining the data execution module matched with each executable network address group in the executable network address groups in the data execution module list as a matched data module to obtain a matched data module list. The matching may be that the executable network address is the same as the data execution network address included in the data execution module, and the data service name corresponding to the executable network address is the same as the data event name corresponding to the data execution network address.
In some embodiments, the execution subject may perform a data event execution operation on a message in the message queue corresponding to the data event to be executed based on the matching data module list. First, the matching data modules in the matching data module list may be sorted according to an execution sequence of the executable network addresses represented by the data event execution numbers included in the data event to be executed. And then, sending the messages corresponding to the data events to be executed to a matching data module according to the sequence so as to execute the data events.
As an example, the data event performing operation may be the server deducting the quantity of the item in the user order from the item inventory. Or the server side deletes the item purchase list of the user.
In some optional implementation manners of some embodiments, the matching data module in the matching data module list may further include a data service address, an event request timeout duration, an event execution method type, a data event request header, a data event request parameter, and data service response policy information. The data service response policy information may include a data service response number. The executing agent performs a data event executing operation on the message corresponding to the data event to be executed in the message queue based on the matching data service list, and may include the following steps:
firstly, performing network service request configuration on a data service name, a data service address, an event request timeout duration, an event execution method type, a data event request header, a data event request parameter and data service response strategy information which are included in each matching data module in the matching data module list to generate a network service request, and obtaining a network service request list. The time request timeout duration can be used as a maximum timeout duration condition, and is used for sending request timeout information to the user side after the data event request is overtime. The time execution method type may be a post request type or a get request type. The data event request parameter may be a parameter of the data event that requires processing to perform (e.g., the amount of items that need to be subtracted from inventory, or the number of inventory that needs to be deleted, etc.). The data service response policy information may be an execution sequence number of the matching data module. The data service name, the data service address, the event request timeout duration, the event execution method type, the data event request header, the data event request parameter, and the data service response policy information included in the matching data module may be configured as a network service request packet, which is used as a network service request. Thereby, a network service request list can be obtained.
And secondly, according to the data service response number corresponding to each network service request in the network service request list, sending each network service request in the network service request list to a data service address included in the network service request for performing data event execution operation.
Optionally, the executing main body may further perform the following steps:
firstly, acquiring an operation result set of the data event execution operation. Each operation result in the operation result set may include an execution duration, an execution result, an execution service request parameter, and an execution service response parameter of the matching data service corresponding to the operation result. The execution result can be used for representing the success or failure of the execution of the data event. The executive service request parameter may be the same data as the data event request parameter described above. The executive service response parameter may be used to characterize the data after the execution of the completed data event (e.g., may be the amount of inventory after the deduction, or the amount of value flow, etc.).
And secondly, generating a data time execution link for query based on the operation result set. The operation results in the operation result set may be arranged into associated nodes according to the execution order. The data included in the operation result can then be filled into the associated nodes to construct an execution link for the user to query.
As can be seen from fig. 3, compared with the description of some embodiments corresponding to fig. 2, the flow 300 of the data event execution method in some embodiments corresponding to fig. 3 embodies the steps of updating the message queue and performing the data event execution operation. By introducing the data event list and the data execution module list, the data execution module for executing the data event can be updated without actively modifying the business logic of the user side after the business requirement is changed (for example, adding the function of sending the execution result of the data event). And then after the user side is started, adapting the data execution module which can be used for executing the data event through the mapping relation between the data execution module and the data event. Therefore, when the user side is started each time, the matched data module required after the service requirement is changed can be dynamically generated, so that the data event execution operation is completed. The situation that when the service requirement (for example, adding the data event execution result sending function) is changed, the service logic of the user side needs to be actively modified to continue the data event request operation is avoided, so that the decoupling between the user side and the server side is realized, and the efficiency of executing the data event is further improved.
With further reference to fig. 4, as an implementation of the methods shown in the above figures, the present disclosure provides some embodiments of a data event execution apparatus, which correspond to those of the method embodiments shown in fig. 2, and which may be applied in various electronic devices in particular.
As shown in fig. 4, the data event execution apparatus 400 of some embodiments includes: an acquisition unit 401, a matching unit 402, an update unit 403, and a data event execution unit 404. The obtaining unit 401 is configured to, in response to monitoring that the user side is started, obtain a data event list; a matching unit 402, configured to, in response to receiving data event request information, match the data event request information with the data event list to obtain a matching result; an updating unit 403 configured to update the message queue based on the data event request information in response to determining that the matching result satisfies a preset condition; a data event executing unit 404, configured to perform a data event executing operation on a message in the message queue corresponding to the data event request information according to a data executing module in a preset data executing module list.
It will be understood that the elements described in the apparatus 400 correspond to various steps in the method described with reference to fig. 2. Thus, the operations, features and resulting advantages described above with respect to the method are also applicable to the apparatus 400 and the units included therein, and will not be described herein again.
Referring now to FIG. 5, a block diagram of an electronic device (e.g., computing device 101 of FIG. 1) 500 suitable for use in implementing some embodiments of the present disclosure is shown. The electronic device shown in fig. 5 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 5, electronic device 500 may include a processing means (e.g., central processing unit, graphics processor, etc.) 501 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM) 502 or a program loaded from a storage means 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data necessary for the operation of the electronic apparatus 500 are also stored. The processing device 501, the ROM 502, and the RAM 503 are connected to each other through a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
Generally, the following devices may be connected to the I/O interface 505: input devices 506 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 507 including, for example, a Liquid Crystal Display (LCD), speakers, vibrators, and the like; storage devices 508 including, for example, magnetic tape, hard disk, etc.; and a communication device 509. The communication means 509 may allow the electronic device 500 to communicate with other devices wirelessly or by wire to exchange data. While fig. 5 illustrates an electronic device 500 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided. Each block shown in fig. 5 may represent one device or may represent multiple devices as desired.
In particular, according to some embodiments of the present disclosure, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, some 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 illustrated in the flow chart. In some such embodiments, the computer program may be downloaded and installed from a network via the communication means 509, or installed from the storage means 508, or installed from the ROM 502. The computer program, when executed by the processing device 501, performs the above-described functions defined in the methods of some embodiments of the present disclosure.
It should be noted that the computer readable medium described above in some embodiments of the present disclosure may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination 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 some embodiments of the 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. In some embodiments of the present disclosure, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. 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, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.
The computer readable medium may be embodied in the apparatus; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: responding to the monitoring of the starting of the user side, and acquiring a data event list; in response to receiving data event request information, matching the data event request information with the data event list to obtain a matching result; updating a message queue based on the data event request information in response to determining that the matching result meets a preset condition; and performing data event execution operation on the message corresponding to the data event request information in the message queue according to a data execution module in a preset data execution module list.
Computer program code for carrying out operations for embodiments of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart 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 disclosure. 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 described in some embodiments of the present disclosure may be implemented by software, and may also be implemented by hardware. The described units may also be provided in a processor, and may be described as: a processor includes an acquisition unit, a matching unit, an updating unit, and a data event execution unit. Where the names of these units do not in some cases constitute a limitation of the unit itself, for example, the acquisition unit may also be described as a "unit to acquire a data event list".
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention in the embodiments of the present disclosure is not limited to the specific combination of the above-mentioned features, but also encompasses other embodiments in which any combination of the above-mentioned features or their equivalents is made without departing from the inventive concept as defined above. For example, the above features and (but not limited to) technical features with similar functions disclosed in the embodiments of the present disclosure are mutually replaced to form the technical solution.
Claims (10)
1. A data event execution method, comprising:
responding to the monitoring of the starting of the user side, and acquiring a data event list;
in response to receiving the data event request information, matching the data event request information with the data event list to obtain a matching result;
updating a message queue based on the data event request information in response to determining that the matching result meets a preset condition;
and performing data event execution operation on the message corresponding to the data event request information in the message queue according to a data execution module in a preset data execution module list.
2. The method of claim 1, wherein before the matching the data event request information with the data event list to obtain a matching result, the method further comprises:
in response to the data event list, updating a local event list by using the data event list to obtain an updated event list;
and storing the updated event list to a local cache.
3. The method of claim 1, wherein the data event request information includes an event request address, the data events in the data event list include executable network addresses; and
the matching the data event request information with the data event list includes:
and matching an event request address in the data event request information with each executable network address in the data event list, wherein the matching is that the event request address is the same as at least one executable network address in the data event list, and the mismatching is that the event request address is different from each executable network address in the data event list.
4. The method of claim 3, wherein said updating a message queue based on said data event request information comprises:
in response to determining that the data event request information matches the data event list, determining a data event name, a data event service address, and data event execution policy information for the data event request information;
configuring an event request address, the data event name, a data event service address and data event execution policy information included in the data event request information as a data event to be executed, and adding the data event to be executed to the message queue.
5. The method of claim 4, wherein the data execution modules in the list of data execution modules include data service names; and
the performing, by the data execution module in the preset data execution module list, a data event execution operation on the message corresponding to the data event request information in the message queue includes:
selecting a data execution module matched with the data event to be executed from the preset data execution module list as a matched data module to obtain a matched data module list, wherein the data service name included by the matched data module in the matched data module list is the same as the data event name included by the data event to be executed;
and performing data event execution operation on the message corresponding to the data event to be executed in the message queue based on the matched data module list.
6. The method of claim 5, wherein the matched data modules in the list of matched data modules further comprise a data service address, an event request timeout duration, an event execution method type, a data event request header, a data event request parameter, and data service response policy information, the data service response policy information comprising a data service response number; and
the performing a data event execution operation on the message corresponding to the data event to be executed in the message queue based on the matching data module list includes:
performing network service request configuration on a data service name, a data service address, event request timeout duration, an event execution method type, a data event request header, data event request parameters and data service response strategy information which are included in each matched data module in the matched data module list to generate a network service request, so as to obtain a network service request list;
and according to the data service response number corresponding to each network service request in the network service request list, sending each network service request in the network service request list to a data service address included in the network service request for performing data event execution operation.
7. The method of claim 6, wherein the method further comprises:
acquiring an operation result set of the data event execution operation, wherein each operation result in the operation result set comprises an execution duration, an execution result, an execution service request parameter and an execution service response parameter of a matched data module corresponding to the operation result;
and generating a data time execution link for query based on the operation result set.
8. A data event execution apparatus, comprising:
the acquisition unit is configured to respond to the monitoring of the starting of the user terminal and acquire a data event list;
the matching unit is configured to respond to the received data event request information, match the data event request information with the data event list and obtain a matching result;
an updating unit configured to update a message queue based on the data event request information in response to determining that the matching result satisfies a preset condition;
and the data event execution unit is configured to perform data event execution operation on the message corresponding to the data event request information in the message queue according to a data execution module in a preset data execution module list.
9. An electronic device, comprising:
one or more processors;
a storage device having one or more programs stored thereon,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.
10. A computer-readable medium, on which a computer program is stored, wherein the program, when executed by a processor, implements the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111104631.4A CN113553206B (en) | 2021-09-22 | 2021-09-22 | Data event execution method and device, electronic equipment and computer readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111104631.4A CN113553206B (en) | 2021-09-22 | 2021-09-22 | Data event execution method and device, electronic equipment and computer readable medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113553206A true CN113553206A (en) | 2021-10-26 |
| CN113553206B CN113553206B (en) | 2021-12-21 |
Family
ID=78106480
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111104631.4A Active CN113553206B (en) | 2021-09-22 | 2021-09-22 | Data event execution method and device, electronic equipment and computer readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113553206B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20230229533A1 (en) * | 2022-01-17 | 2023-07-20 | Fujitsu Limited | Control method, computer-readable recording medium storing control program, and information processing apparatus |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060109857A1 (en) * | 2004-11-19 | 2006-05-25 | Christian Herrmann | System, method and computer program product for dynamically changing message priority or message sequence number in a message queuing system based on processing conditions |
| CN109508244A (en) * | 2018-10-18 | 2019-03-22 | 北京新唐思创教育科技有限公司 | Data processing method and computer-readable medium |
| CN110968438A (en) * | 2019-11-29 | 2020-04-07 | 江苏满运软件科技有限公司 | Asynchronous notification method and device of event message, electronic equipment and storage medium |
| CN111723134A (en) * | 2019-03-19 | 2020-09-29 | 北京京东尚科信息技术有限公司 | Information processing method, information processing device, electronic equipment and storage medium |
| CN111949654A (en) * | 2020-07-20 | 2020-11-17 | 上海淇馥信息技术有限公司 | User label-based quick query method and system and electronic equipment |
| CN112416632A (en) * | 2020-12-14 | 2021-02-26 | 五八有限公司 | Event communication method and device, electronic equipment and computer readable medium |
| CN112765520A (en) * | 2021-01-20 | 2021-05-07 | 三六零视觉(北京)科技有限公司 | Message pushing method, device, equipment and storage medium |
-
2021
- 2021-09-22 CN CN202111104631.4A patent/CN113553206B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060109857A1 (en) * | 2004-11-19 | 2006-05-25 | Christian Herrmann | System, method and computer program product for dynamically changing message priority or message sequence number in a message queuing system based on processing conditions |
| CN109508244A (en) * | 2018-10-18 | 2019-03-22 | 北京新唐思创教育科技有限公司 | Data processing method and computer-readable medium |
| CN111723134A (en) * | 2019-03-19 | 2020-09-29 | 北京京东尚科信息技术有限公司 | Information processing method, information processing device, electronic equipment and storage medium |
| CN110968438A (en) * | 2019-11-29 | 2020-04-07 | 江苏满运软件科技有限公司 | Asynchronous notification method and device of event message, electronic equipment and storage medium |
| CN111949654A (en) * | 2020-07-20 | 2020-11-17 | 上海淇馥信息技术有限公司 | User label-based quick query method and system and electronic equipment |
| CN112416632A (en) * | 2020-12-14 | 2021-02-26 | 五八有限公司 | Event communication method and device, electronic equipment and computer readable medium |
| CN112765520A (en) * | 2021-01-20 | 2021-05-07 | 三六零视觉(北京)科技有限公司 | Message pushing method, device, equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20230229533A1 (en) * | 2022-01-17 | 2023-07-20 | Fujitsu Limited | Control method, computer-readable recording medium storing control program, and information processing apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113553206B (en) | 2021-12-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110311983B (en) | Service request processing method, device and system, electronic equipment and storage medium | |
| WO2021051747A1 (en) | Data update method, system and device, electronic device, and computer storage medium | |
| CN110781373B (en) | List updating method and device, readable medium and electronic equipment | |
| CN112416632B (en) | Event communication method and device, electronic equipment and computer readable medium | |
| CN113760536A (en) | Data caching method and device, electronic equipment and computer readable medium | |
| CN113553206B (en) | Data event execution method and device, electronic equipment and computer readable medium | |
| CN116743785A (en) | Cloud network data storage method, device, equipment and medium based on fog calculation | |
| CN112507676B (en) | Method and device for generating energy report, electronic equipment and computer readable medium | |
| CN113824675B (en) | Method and device for managing login state | |
| CN114115941A (en) | Resource sending method, page rendering method, device, electronic equipment and medium | |
| CN113760929A (en) | Data synchronization method and device, electronic equipment and computer readable medium | |
| CN113760927A (en) | Data processing method and device, electronic equipment and computer readable medium | |
| CN113378041A (en) | Prompt message pushing method and device, electronic equipment and computer readable medium | |
| CN112311840A (en) | Multi-terminal data synchronization method, device, equipment and medium | |
| CN113342837B (en) | Data transmission method, device, electronic equipment and computer readable medium | |
| CN111314457B (en) | Method and device for setting virtual private cloud | |
| CN113472565B (en) | Method, apparatus, device and computer readable medium for expanding server function | |
| US20240152504A1 (en) | Data interaction method, apparatus, and electronic device | |
| CN112311833B (en) | Data updating method and device | |
| CN110262756B (en) | Method and device for caching data | |
| CN114444064A (en) | Account processing method and device, electronic equipment and computer readable medium | |
| CN114398437A (en) | User information processing method and device, electronic equipment and computer readable medium | |
| CN113626664A (en) | House resource screening information processing method, device, equipment and computer readable medium | |
| CN118590488A (en) | Information processing method, device, system and electronic equipment | |
| CN116599846A (en) | Inter-tenant network connection method, inter-tenant network connection device, electronic equipment and computer readable medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: No.3-8-132, 1st floor, building 3, Fuqian street, Huairou District, Beijing Patentee after: Beijing Defeng Xinzheng Technology Co.,Ltd. Address before: Room 501, 5 / F, Hall B, building 8, yard 1, Jiuxianqiao East Road, Chaoyang District, Beijing 100015 Patentee before: Beijing Defeng new journey Technology Co.,Ltd. |