[go: up one dir, main page]

CN115617541A - Communication method and event center scheduling system - Google Patents

Communication method and event center scheduling system Download PDF

Info

Publication number
CN115617541A
CN115617541A CN202211226312.5A CN202211226312A CN115617541A CN 115617541 A CN115617541 A CN 115617541A CN 202211226312 A CN202211226312 A CN 202211226312A CN 115617541 A CN115617541 A CN 115617541A
Authority
CN
China
Prior art keywords
message
event
subscription
scheduling system
subscription message
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.)
Pending
Application number
CN202211226312.5A
Other languages
Chinese (zh)
Inventor
李京
陈云中
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hunan MgtvCom Interactive Entertainment Media Co Ltd
Original Assignee
Hunan MgtvCom Interactive Entertainment Media Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Hunan MgtvCom Interactive Entertainment Media Co Ltd filed Critical Hunan MgtvCom Interactive Entertainment Media Co Ltd
Priority to CN202211226312.5A priority Critical patent/CN115617541A/en
Publication of CN115617541A publication Critical patent/CN115617541A/en
Pending legal-status Critical Current

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/542—Event management; Broadcasting; Multicasting; Notifications
    • 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/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/5038—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration
    • 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/546—Message passing systems or structures, e.g. queues
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The application discloses a communication method and an event center scheduling system. The communication method comprises the following steps: receiving a subscription message sent by a first object, wherein the subscription message carries a closure; determining a second object subscribed to the subscription message based on the identification of the subscription message; sending the subscription message to a second object; receiving a response message sent by the second object, wherein the response message is generated and sent by calling the closure by the second object and comprises an execution result of the second object for the subscription message; a reply message is sent to the first object. Based on the technical scheme disclosed by the application, high-efficiency communication between the objects can be realized, and the coupling degree between the objects is reduced. In addition, by establishing a feedback channel between the subscribed and the subscriber, the subscribed can know the processing condition of the subscriber for the subscription message.

Description

Communication method and event center scheduling system
Technical Field
The application belongs to the technical field of software development, and particularly relates to a communication method and an event center scheduling system.
Background
In software development, communication is required between multiple objects (e.g., components). At present, communication among a plurality of objects is mainly realized by means of broadcast messages and proxy agents. However, these two schemes have problems of low communication efficiency and large degree of coupling between objects.
Disclosure of Invention
In view of the above, an object of the present invention is to provide a communication method and an event hub scheduling system, which can achieve efficient communication between objects and reduce the degree of coupling between the objects.
In order to achieve the above purpose, the present application provides the following technical solutions:
in a first aspect, the present application provides a communication method applied to an event hub scheduling system, where the communication method includes:
receiving a subscription message sent by a first object, wherein the subscription message carries a closure;
determining a second object subscribed to the subscription message based on the identification of the subscription message;
sending the subscription message to the second object;
receiving a response message sent by the second object, wherein the response message is generated and sent by the second object based on the closure, and the response message contains an execution result of the second object on the subscription message;
sending the reply message to the first object.
Optionally, the event hub scheduling system stores a pre-constructed static event, where the static event includes a plurality of tasks, and the communication method further includes:
receiving an instruction indicating to initiate a static event;
and scheduling related objects to execute the tasks based on the execution priorities of the tasks, wherein during the execution of each task, a message is sent to the object executing the task, and a message returned by the object executing the task is received.
Optionally, in a case that the plurality of tasks have the same execution priority, the related objects are scheduled to execute the plurality of tasks having the same execution priority in parallel.
Optionally, on the basis of the communication method, the method further includes:
releasing the subscription event for the second object when the second object is released.
Optionally, on the basis of the communication method, the method further includes:
receiving configuration information sent by an object, wherein the configuration information comprises an identifier of the object and an identifier of a message subscribed by the object;
and establishing and storing the corresponding relation between the identification of the object and the identification of the subscribed message.
In a second aspect, the present application provides an event hub scheduling system, comprising:
a subscription message receiving unit, configured to receive a subscription message sent by a first object, where the subscription message carries a closure;
an object determination unit, configured to determine a second object subscribed to the subscription message based on the identifier of the subscription message;
a subscription message sending unit, configured to send the subscription message to the second object;
a response message receiving unit, configured to receive a response message sent by the second object, where the response message is generated and sent by the second object based on the closure, and the response message includes an execution result of the second object for the subscription message;
a response message sending unit for sending the response message to the first object.
Optionally, the event hub scheduling system stores a pre-constructed static event, where the static event includes a plurality of tasks, and the event hub scheduling system further includes:
an instruction receiving unit, configured to receive an instruction indicating to start a static event;
and the scheduling unit is used for scheduling related objects to execute each task based on the execution priority of the tasks, wherein during the execution of each task, a message is sent to the object executing the task, and a message returned by the object executing the task is received.
Optionally, when the plurality of tasks have the same priority, the scheduling unit schedules the related object to execute the plurality of tasks having the same execution priority in parallel.
Optionally, on the basis of the event hub scheduling system, further setting:
and the subscription event releasing unit is used for releasing the subscription event of the second object when the second object is released.
Optionally, on the basis of the event hub scheduling system, further setting:
the device comprises a preprocessing unit, a processing unit and a processing unit, wherein the preprocessing unit is used for receiving configuration information sent by an object, and the configuration information comprises an identifier of the object and an identifier of a message subscribed by the object; and establishing and storing the corresponding relation between the identification of the object and the identification of the subscribed message.
Therefore, the beneficial effects of the application are as follows:
according to the communication method disclosed by the application, the subscribed information is sent to the event hub scheduling system by the subscriber, the subscriber of the subscribed information is determined by the event hub scheduling system based on the identification of the subscribed information, and the subscribed information is sent to the subscriber, so that high-efficiency communication between objects is realized, and the coupling degree between the objects is reduced. In addition, the subscription message carries the closure, which enables the subscriber to feed back the execution result for the subscription message to the subscribed user based on the closure, that is, the subscribed user can know the processing condition of the subscriber for the subscription message by establishing a feedback channel between the subscribed user and the subscriber.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following descriptions are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a flow chart of a communication method disclosed herein;
FIG. 2 is an architecture diagram of a communication system as disclosed herein;
FIG. 3 is a schematic diagram of an event hub scheduling system according to the present disclosure executing a static event;
FIG. 4 is a block diagram of an event hub scheduling system according to the present disclosure;
FIG. 5 is a block diagram of another event hub scheduling system disclosed herein.
Detailed Description
The application discloses a communication method and an event center scheduling system, which can realize high-efficiency communication among objects and can reduce the coupling degree among the objects.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a flow chart of a communication method disclosed in the present application. The communication method is performed by Ecedis (Event Central Dispatch System). The communication method comprises the following steps:
s101: and receiving a subscription message sent by the first object.
Wherein the subscription message carries a closure. The closure contains callback functions that can be executed by other objects.
For convenience of description, an object that sends a subscription message to Ecedis is referred to as a first object, and the first object may also be referred to as a subscriber.
It should be noted that the subscription message sent by each object has a unique identifier. An object in the present application may be a component.
S102: a second object subscribed to the subscription message is determined based on the identification of the subscription message.
The Ecedis stores the identification of the subscription message to which each object subscribes. After receiving the subscription message sent by the first object, the Ecedis finds out which objects subscribe to the subscription message based on the identification of the subscription message. For convenience of description, an object subscribed to the foregoing subscription message is referred to as a second object.
S103: the subscription message is sent to the second object.
S104: and receiving a response message sent by the second object.
And the response message is generated and sent by the second object based on the closure in the subscription message, and the response message contains the execution result of the second object on the subscription message.
In implementation, the first object indicates, by means of the closure, the data that the subscriber needs to contain for the execution result of the feedback. That is, the closure generated by the first object contains indication information of data required to contain the execution result fed back by the subscriber.
For example, the closure generated by the first object contains: the execution result fed back by the subscriber needs to include indication information of whether the execution of the subscription message is successful. Correspondingly, the execution result in the response message generated by the second object is: information characterizing the successful execution of the subscription message (e.g., boolean value true) or information characterizing the unsuccessful execution of the subscription message (e.g., boolean value false).
As another example, the closure generated by the first object includes: the execution result fed back by the subscriber needs to include indication information of the operation result. Correspondingly, the execution result in the response message generated by the second object is: the operation result for the subscription message is usually a character string. For example, the function of the second object is to perform a specific operation on the input parameters (obtained from the subscription message sent by the first object) to obtain an operation result, and then the execution result in the response message generated by the second object is the aforementioned operation result.
S105: a reply message is sent to the first object.
In the communication method disclosed by the application, a feedback channel is designed so that a subscriber knows the processing condition of the subscriber for the subscription message. Specifically, after receiving the subscription message, the second object (subscriber) needs to feed back a message to the first object (i.e., the subscriber), so that the first object knows the execution result of the second object for the subscription message.
According to the communication method, the subscribed information is sent to the event center scheduling system by the subscribed user, the event center scheduling system determines the subscribed user of the subscribed information based on the identification of the subscribed information and sends the subscribed information to the subscribed user, so that high-efficiency communication between objects is achieved, and the coupling degree between the objects is reduced. In addition, the subscription message carries the closure, which enables the subscriber to feed back the execution result for the subscription message to the subscribed user based on the closure, that is, the subscribed user can know the processing condition of the subscriber for the subscription message by establishing a feedback channel between the subscribed user and the subscriber.
Fig. 2 shows an architecture of a communication system built based on an event hub scheduling system. It can be seen that any two objects in the communication system can communicate with each other through the event hub scheduling system without coupling between the objects.
In another embodiment of the present application, an event hub scheduling system stores pre-constructed static events, wherein each static event comprises a plurality of tasks. In the process of constructing the static event in advance, it is necessary to determine which tasks the static event contains, and configure the execution priority of each task.
Correspondingly, on the basis of the communication method disclosed by the application, the event hub scheduling system further comprises the following steps:
a1: receiving an instruction indicating to initiate a static event;
a2: based on the execution priorities of the tasks included in the static event, the related objects are scheduled to execute the tasks. During the execution of each task, the event hub scheduling system sends a message to an object executing the task and receives a message returned by the object executing the task.
It should be noted that, among a plurality of tasks included in one static event, there may be a case where some tasks have the same execution priority. Alternatively, if multiple tasks have the same execution priority, the event hub scheduling system schedules the associated object to execute the multiple tasks with the same execution priority in parallel to reduce the time taken to complete the static event.
In the communication method disclosed in the above embodiment of the present application, an event static scheduling pattern is introduced. And for the event with fixed functions, determining the tasks contained in the event, and configuring the execution priority of each task, so that the event is assembled into a task chain to be executed. And after receiving an instruction for indicating to start the static event, the event hub scheduling system schedules the related objects to execute each task based on the execution priority of each task. In the process, the event hub scheduling system sends a message to the object executing the task and receives a message returned by the object executing the task, and each object only needs to process the task related to the object and does not need to pay attention to the processing condition of the whole static event.
Referring to FIG. 3, FIG. 3 shows the flow of the event hub scheduling system executing a static event.
The static event comprises a task A, a task B1, a task B2, a task B3 and a task C, wherein the priority of each task is as follows: task a > task B1= task B2= task B3 > task C. After receiving an instruction indicating to start a static event, the event hub scheduling system calls a related object to execute a task A, and in the process of executing the task A, the event hub scheduling system sends a message to the object executing the task A and receives a message returned by the object executing the task A; after the task A is executed, the event center scheduling system calls related objects to execute the task B1, the task B2 and the task B3 in parallel, and in the process, the event center scheduling system sends messages to the objects for executing the task B1, the task B2 and the task B3 and receives messages returned by the objects; and after the task B1, the task B2 and the task B3 are executed, the event hub scheduling system calls a related object to execute the task C, in the process, the event hub scheduling system sends a message to the object executing the task C and receives a message returned by the object executing the task C, and after the task C is executed, the static event is finished.
In another embodiment of the present application, on the basis of the above-disclosed communication methods of the present application, the method further includes: when the second object is released, the event hub scheduling system unsubscribes the second object from the event.
It should be noted that, when an object is released, the space occupied by the object in the memory is recycled.
Assume that object C subscribes to the events of object A and object B. When the object C is released, the memory space occupied by the object C is recycled, and the memory space originally occupied by the object C may be empty or may be allocated to another object. If the subscription event of the object C is not timely cancelled, when the object a or the object B issues the subscription message, the subscription message is sent to the memory space originally occupied by the object C, which may cause a wild pointer or crash. In the application, after a certain object is released, the event hub scheduling system automatically releases all subscribed events of the object without the need of technical personnel for processing, so that the burden of the technical personnel is reduced.
It should be noted that, the event hub scheduling system stores the identifier of the subscription message subscribed by each object. The event hub scheduling system unsubscribes the second object from the event may be: the event hub scheduling system deletes the stored identification of the subscription message to which the second object subscribes.
In the communication method disclosed in the above embodiment of the present application, when a subscriber is released, the event hub scheduling system automatically removes all messages and events subscribed by the subscriber, thereby avoiding the problems of wild pointers, collapse and the like, improving the stability of the system, and reducing the burden of technicians without the participation of technicians.
In another embodiment of the present application, on the basis of the communication method disclosed above, the method further includes:
b1: the event-driven scheduling system receives configuration information sent by an object, wherein the configuration information comprises an identification of the object and an identification of a message subscribed by the object.
B2: and establishing and storing the corresponding relation between the identification of the object and the identification of the subscribed message.
After receiving the subscription message sent by the object, the event-driven scheduling system searches which objects subscribe the subscription message based on the identifier of the subscription message and the corresponding relationship.
In the above embodiment, the releasing of the subscription event of the second object by the event hub scheduling system is: and deleting the stored corresponding relation containing the identification of the second object by the event hub scheduling system.
The present application also discloses an event hub scheduling system, the structure of which is shown in fig. 4, and the system includes a subscription message receiving unit 10, an object determining unit 20, a subscription message sending unit 30, a response message receiving unit 40, and a response message sending unit 50.
Wherein:
a subscription message receiving unit 10, configured to receive a subscription message sent by a first object. Wherein the subscription message carries a closure.
An object determining unit 20, configured to determine a second object subscribed to the subscription message based on the identifier of the subscription message.
A subscription message sending unit 30, configured to send a subscription message to the second object.
And a response message receiving unit 40, configured to receive a response message sent by the second object. And generating and sending a response message by the second object based on the closure in the subscription message, wherein the response message comprises the execution result of the second object for the subscription message.
A response message sending unit 50 for sending a response message to the first object.
The event hub scheduling system disclosed by the application receives a subscription message sent by a subscriber, determines the subscriber of the subscription message based on the identifier of the subscription message, sends the subscription message to the subscriber, receives a response message sent by the subscriber, and sends the response message to the subscriber. The event-based hub scheduling system realizes high-efficiency communication between objects and reduces the coupling degree between the objects. In addition, the subscription message carries the closure, which enables the subscriber to feed back the execution result for the subscription message to the subscribed user based on the closure, that is, the subscribed user can know the processing condition of the subscriber for the subscription message by establishing a feedback channel between the subscribed user and the subscriber.
In another embodiment of the present application, the event hub scheduling system stores a pre-constructed static event, the static event includes a plurality of tasks, and further includes an instruction receiving unit 60 and a scheduling unit 70, as shown in fig. 5.
An instruction receiving unit 60 is configured to receive an instruction indicating to start a static event.
And a scheduling unit 70, configured to schedule the relevant objects to execute each task based on the execution priorities of the multiple tasks, wherein during the execution of each task, a message is sent to the object executing the task, and a message returned by the object executing the task is received.
Alternatively, in the case that a plurality of tasks have the same priority, the scheduling unit 70 schedules the related object to execute a plurality of tasks having the same execution priority in parallel, so as to shorten the time taken to complete the static event.
In another embodiment of the present application, a subscription event release unit is further provided on the basis of the event hub scheduling system of fig. 4 and 5.
The subscription event releasing unit is used for: and releasing the subscription event of the second object when the second object is released.
In another embodiment of the present application, a preprocessing unit is further provided on the basis of each of the event hub scheduling systems disclosed above.
The preprocessing unit is used for: receiving configuration information sent by an object, wherein the configuration information comprises an identifier of the object and an identifier of a message subscribed by the object; and establishing and storing the corresponding relation between the identification of the object and the identification of the subscribed message.
It should be noted that, technical features described in the embodiments in the specification may be replaced or combined with each other, each embodiment focuses on differences from other embodiments, and the same or similar parts in the embodiments may be referred to each other. The steps in the method of the embodiments of the present application may be sequentially adjusted, combined, and deleted according to actual needs. The modules and sub-modules in the device and the equipment in the embodiments of the present application can be combined, divided and deleted according to actual needs.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus, device and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a module or a sub-module may be divided into only one type of logical function, and another division may be implemented in practice, for example, a plurality of sub-modules or modules may be combined or integrated into another module, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
The modules or sub-modules described as separate parts may or may not be physically separate, and parts that are modules or sub-modules may or may not be physical modules or sub-modules, may be located in one place, or may be distributed over a plurality of network modules or sub-modules. Some or all of the modules or sub-modules can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional modules or sub-modules in the embodiments of the present application may be integrated into one processing module, or each module or sub-module may exist alone physically, or two or more modules or sub-modules are integrated into one module. The integrated modules or sub-modules may be implemented in the form of hardware, or may be implemented in the form of software functional modules or sub-modules.
It is further noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.
The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. For the event hub scheduling system disclosed by the embodiment, the description is simple because the event hub scheduling system corresponds to the communication method disclosed by the embodiment, and the relevant points can be referred to the method part for explanation.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. A communication method is applied to an event hub scheduling system, and comprises the following steps:
receiving a subscription message sent by a first object, wherein the subscription message carries a closure;
determining a second object subscribed to the subscription message based on the identification of the subscription message;
sending the subscription message to the second object;
receiving a response message sent by the second object, wherein the response message is generated and sent by the second object based on the closure, and the response message contains an execution result of the second object on the subscription message;
sending the reply message to the first object.
2. The communication method according to claim 1, wherein the event hub scheduling system stores a pre-constructed static event, the static event comprising a plurality of tasks, the communication method further comprising:
receiving an instruction indicating to initiate a static event;
and scheduling related objects to execute each task based on the execution priority of the tasks, wherein during the execution of each task, a message is sent to the object executing the task, and a message returned by the object executing the task is received.
3. The communication method according to claim 2, wherein in a case where the plurality of tasks have the same execution priority, the related objects are scheduled to execute the plurality of tasks having the same execution priority in parallel.
4. A communication method according to claim 1, 2 or 3, further comprising:
releasing the subscription event for the second object when the second object is released.
5. The communication method of claim 1, further comprising:
receiving configuration information sent by an object, wherein the configuration information comprises an identifier of the object and an identifier of a message subscribed by the object;
and establishing and storing the corresponding relation between the identification of the object and the identification of the subscribed message.
6. An event hub scheduling system, comprising:
a subscription message receiving unit, configured to receive a subscription message sent by a first object, where the subscription message carries a closure;
an object determination unit, configured to determine a second object subscribed to the subscription message based on the identifier of the subscription message;
a subscription message sending unit, configured to send the subscription message to the second object;
a response message receiving unit, configured to receive a response message sent by the second object, where the response message is generated and sent by the second object based on the closure, and the response message includes an execution result of the second object for the subscription message;
a response message sending unit for sending the response message to the first object.
7. The event hub scheduling system of claim 6 wherein the event hub scheduling system stores a pre-built static event, the static event comprising a plurality of tasks, the event hub scheduling system further comprising:
the instruction receiving unit is used for receiving an instruction for starting the static event;
and the scheduling unit is used for scheduling related objects to execute each task based on the execution priority of the tasks, wherein during the execution of each task, a message is sent to the object executing the task, and a message returned by the object executing the task is received.
8. The event hub scheduling system of claim 7, wherein:
in case that a plurality of tasks have the same priority, the scheduling unit schedules the associated object to execute the plurality of tasks having the same execution priority in parallel.
9. The event hub scheduling system of claim 6, 7 or 8 further comprising:
and the subscription event releasing unit is used for releasing the subscription event of the second object when the second object is released.
10. The event hub scheduling system of claim 6 further comprising:
the device comprises a preprocessing unit, a processing unit and a processing unit, wherein the preprocessing unit is used for receiving configuration information sent by an object, and the configuration information comprises an identifier of the object and an identifier of a message subscribed by the object; and establishing and storing the corresponding relation between the identification of the object and the identification of the subscribed message.
CN202211226312.5A 2022-10-09 2022-10-09 Communication method and event center scheduling system Pending CN115617541A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211226312.5A CN115617541A (en) 2022-10-09 2022-10-09 Communication method and event center scheduling system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211226312.5A CN115617541A (en) 2022-10-09 2022-10-09 Communication method and event center scheduling system

Publications (1)

Publication Number Publication Date
CN115617541A true CN115617541A (en) 2023-01-17

Family

ID=84861166

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211226312.5A Pending CN115617541A (en) 2022-10-09 2022-10-09 Communication method and event center scheduling system

Country Status (1)

Country Link
CN (1) CN115617541A (en)

Similar Documents

Publication Publication Date Title
CN110290180B (en) Distributed task scheduling method and device, computer equipment and storage medium
CN109347934B (en) Message pushing method and system, server, storage medium and electronic device
CN112099935B (en) Task processing method and device
CN103888619B (en) A message processing method and system thereof
CN111045806A (en) Method and system for realizing delay message queue
CN110471746B (en) Distributed transaction callback method, device and system
CN111210340B (en) Automatic task processing method, device, server and storage medium
CN103810045A (en) Resource allocation method, resource manager, resource server and system
CN112288423A (en) Aggregation payment method and system of distributed framework
CN109858655B (en) Method and system for appointment test
CN111625511A (en) Configuration file management method and device, electronic equipment and storage medium
CN113743879B (en) Automatic rule processing method, system and related equipment
CN113824653A (en) Method and system compatible with multi-protocol service access
CN115617541A (en) Communication method and event center scheduling system
CN112132612A (en) Task processing method and device, electronic equipment and storage medium
CN102215568B (en) Event scheduling control method, device and system
CN115408173A (en) Event processing method and device, electronic equipment and storage medium
CN116303276A (en) Method for realizing file export by spring batch nested script
CN113204434B (en) Planned task execution method and device based on k8s and computer equipment
CN112667384A (en) Task flow scheduling method, device, storage medium and electronic device
CN117640761A (en) Service isolation method and device
GB2289825A (en) Communications system, terminal and method
CN113434316A (en) Function integration method, device, equipment and storage medium based on redis plug-in
CN113141387A (en) Service subscription method, device and system
CN111782352A (en) Service scheduling method and device

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