CN107783849B - Event processing method and client - Google Patents
Event processing method and client Download PDFInfo
- Publication number
- CN107783849B CN107783849B CN201710890729.4A CN201710890729A CN107783849B CN 107783849 B CN107783849 B CN 107783849B CN 201710890729 A CN201710890729 A CN 201710890729A CN 107783849 B CN107783849 B CN 107783849B
- Authority
- CN
- China
- Prior art keywords
- component
- event
- message
- notification message
- message distribution
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 16
- 238000000034 method Methods 0.000 claims abstract description 54
- 230000008569 process Effects 0.000 claims abstract description 24
- 238000012545 processing Methods 0.000 claims description 15
- 238000012544 monitoring process Methods 0.000 claims description 5
- 238000011068 loading method Methods 0.000 claims description 4
- 238000011161 development Methods 0.000 abstract description 9
- 230000006870 function Effects 0.000 description 24
- 238000010586 diagram Methods 0.000 description 8
- 230000009471 action Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
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
Abstract
The invention provides an event processing method and a client, wherein the method is applied to the client, and the client comprises a message distribution component and a plurality of service components. The method comprises the following steps: associating the target business component with the message distribution component to enable the target business component to receive the message sent by the message distribution component; when the target service component monitors an event, the event is transmitted to the message distribution component; when the message distribution component receives the event, sending a notification message corresponding to the event to each associated business component; and each service component receiving the notification message judges whether the notification message comprises identification information associated with each service component, and if so, processes an event corresponding to the notification message. Therefore, the decoupling of the service components is realized, and the development efficiency is improved.
Description
Technical Field
The invention relates to the technical field of software development, in particular to an event processing method and a client.
Background
Currently, in the software development process, a common development method is to develop different service modules for different service functions, and then directly couple a plurality of different service modules together to form an Application (APP).
However, with the superposition of business functions and the increase of functional modules, the coupling level between the modules is deeper and deeper. In the later development, if a certain function needs to be removed, the module corresponding to the function cannot be directly uninstalled, and when the function needs to be updated, the module corresponding to the function cannot be debugged, but the whole application program needs to be debugged.
Disclosure of Invention
In view of the above, the present invention provides an event processing method and a client to solve the above problem.
In order to achieve the above object, an embodiment of the present invention provides an event processing method, which is applied to a client including a message distribution component and a plurality of service components, where the method includes:
associating a target business component with the message distribution component to enable the target business component to receive the message sent by the message distribution component;
when the target business component monitors an event, the event is transmitted to the message distribution component;
after receiving the event, the message distribution component sends a notification message corresponding to the event to each associated service component to notify the corresponding service component to process the event, wherein the notification message comprises identification information associated with the target service component;
and each service component receiving the notification message judges whether the notification message comprises identification information associated with each service component, and if so, processes an event corresponding to the notification message.
Optionally, in the above method, the message distribution component includes a preset collection list;
the step of associating a target business component with the message distribution component includes:
loading a target business component into the aggregate list;
the step of the message distribution component sending the notification message corresponding to the event to each associated business component includes:
the message distribution component sends a notification message corresponding to the event to each business component in the aggregate list.
Optionally, in the above method, the method further comprises:
and removing the designated business component from the set list to release the association of the business component and the message distribution component, so that the business component cannot receive the notification message sent by the message distribution component.
Optionally, in the above method, the step of the target service component transmitting the monitored event to the message distribution component when the target service component monitors the event includes:
and when the target service component monitors the event, calling a broadcast event instruction to transmit the event to the message distribution component.
Optionally, in the method, the step of processing an event corresponding to the notification message includes:
and calling a corresponding functional module to process the event corresponding to the notification message based on the identification information included in the notification message.
The embodiment of the invention also provides a client, which comprises a message distribution component, a plurality of service components and an associated module;
the association module is used for associating a target business component with the message distribution component so that the target business component can receive the message sent by the message distribution component;
the target business component is used for transmitting the event to the message distribution component in a transparent way when monitoring the event;
the message distribution component is used for sending a notification message corresponding to the event to each associated service component after receiving the event so as to notify the corresponding service component to process the event, wherein the notification message comprises identification information associated with the target service component;
and each service component receiving the notification message is used for judging whether the notification message comprises identification information associated with each service component, and if so, processing an event corresponding to the notification message.
Optionally, in the client, the message distribution component includes a preset collection list;
the association module loads the target business component into the aggregate list to associate the target business component with the message distribution component;
and the message distribution component sends a notification message corresponding to the event to each business component in the aggregate list, so that the notification message corresponding to the event is sent to each associated business component.
Optionally, in the client, the client further includes:
and the association releasing module is used for removing the specified business component from the set list so as to release the association between the business component and the message distribution component, so that the business component cannot receive the notification message sent by the message distribution component.
Optionally, in the client, when the target service component monitors an event, the target service component transparently transmits the event to the message distribution component by invoking a broadcast event instruction.
The embodiment of the invention also provides a computer readable storage medium, on which computer instructions are stored, and when the computer instructions are executed, the event processing method provided by the embodiment of the invention is realized.
According to the event processing method and the client provided by the embodiment of the invention, the target service component is associated with the message distribution component, so that the target service component can receive the message sent by the message distribution component. The target service component transmits the monitored events to the message distribution component, and the message distribution component sends notification messages corresponding to the events to each associated service component when receiving the events so as to notify the corresponding service components to process the events. And each service component receiving the notification message judges whether the notification message comprises identification information associated with each service component, and if so, processes an event corresponding to the notification message. By the design, decoupling of the service components is achieved, and development efficiency is improved.
In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1 is a schematic block diagram of an electronic terminal according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of an event processing method according to an embodiment of the present invention;
fig. 3 is a functional block diagram of a client according to an embodiment of the present invention;
fig. 4 is a block diagram of another functional module of the client according to an embodiment of the present invention.
Icon: 100-an electronic terminal; 110-a memory; 120-a processor; 200-a client; 210-a message distribution component; 220-a business component; 230-an association module; 240 — disassociation module.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. 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 invention.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
As shown in fig. 1, fig. 1 is a block diagram of an electronic terminal 100 according to an embodiment of the present invention. The electronic terminal 100 includes a client 200, a memory 110, and a processor 120.
The memory 110, the processor 120 and the elements are electrically connected to each other directly or indirectly to realize data transmission or interaction. The client 200 includes at least one software functional module that can be stored in the memory 110 or solidified in an Operating System (OS) of the electronic terminal 100 in the form of Firmware (Firmware).
In the present embodiment, the electronic terminal 100 may be, but is not limited to, a Personal Computer (PC) smart phone, a tablet Computer, and the like. The client 200 is an APP that can be installed and run in the electronic terminal 100, and the electronic terminal 100 may be an Android system-based terminal.
The Memory 110 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an electrically Erasable Read-Only Memory (EEPROM), and the like.
The processor 120 may be an integrated circuit chip having signal processing capabilities. The Processor 120 may also be a general-purpose Processor, such as a Central Processing Unit (CPU), a Network Processor (NP), etc.; but also digital signal processors (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components; the processor 120 may also be a microprocessor or any conventional processor. The processor 120 may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present invention.
It should be understood that the illustration of fig. 1 is merely an illustration of the electronic terminal 100, and that the electronic terminal 100 may have more or fewer components than those illustrated in fig. 1, or may have a configuration that is completely different from that illustrated in fig. 1. The components shown in fig. 1 may be implemented in software, hardware, or a combination thereof.
The inventor researches and discovers that in the existing software development, corresponding business components 220 are generally developed for different business functions, and then a plurality of different business components 220 are directly coupled together to form an APP. When multiple functional modules are included in a business component 220, the multiple functional modules are also directly coupled together. The direct coupling refers to that when an event is monitored, related service logic is directly processed inside the event, so that a mesh structure is formed among a plurality of service components 220 and among functional modules included in each service component 220.
For example, in the later stage of development, if a certain service component 220 needs to be updated (or uninstalled), because each service component 220 is tightly coupled, a program bug is very easy to occur, and the whole APP needs to be debugged during debugging, which is very low in efficiency. For another example, if a certain function module in a certain service component 220 needs to be updated, corresponding change and debugging need to be performed on the whole APP, so that a change error is easily caused, and the development efficiency is low.
If the service components 220 and the function modules in the service components 220 are developed in a decoupling manner, the development efficiency can be improved, and the maintenance of the code is facilitated.
As shown in fig. 2, the event processing method provided by the embodiment of the present invention is applied to the client 200 shown in fig. 1, where the client 200 includes a message distribution component 210 and a plurality of business components 220. The event handling method will be described in detail below with reference to fig. 2.
Step S110, associating the target service component with the message distribution component 210, so that the target service component can receive the message sent by the message distribution component 210.
The target business component refers to the business component 220 corresponding to the currently needed business function in the plurality of business components 220. The message distribution component 210 may be implemented based on an event bus (EventBus), which is an optimized publish/subscribe message bus, and simplifies communication between components in the APP and between components and background threads.
In implementation, for a business component 220 corresponding to a business function that needs to be used currently, the business component 220 may be associated with the message distribution component 210. If the business component 220 is no longer needed for use, the business component 220 can be disassociated from the message distribution component 210.
In this embodiment, the message distribution component 210 may define a set list modelList, which is used to maintain the service component 220 that needs to be used currently. In detail, the step S110 may be implemented by the following sub-steps:
and loading the target business component into the aggregate list.
Correspondingly, the event processing method may further include the steps of:
the designated business component 220 is removed from the aggregated list to disassociate the business component 220 from the message distribution component 210, thereby disabling the business component 220 from receiving the notification message sent by the message distribution component 210.
In this embodiment, the message distribution component 210 includes a loading method loadModel () and an unloading method unloadModel (). Wherein the load method loadModel () adds a specified service component 220 (e.g., a target service component) to the aggregate list modelList by calling the add () method in the aggregate list modelList. Offload method unloadModel () removes a specified service component 220 (e.g., a target service component) from the aggregate list modelist by calling the remove () method in the aggregate list modelist.
Step S120, when the target service component monitors an event, the target service component transparently transmits the event to the message distribution component 210.
Taking the Android system as an example, the event types include a key event and a screen touch event, and can be monitored through an event monitor.
It should be noted that listener-based event processing generally involves three types of objects: first, an Event Source (Event Source) for generating events, which is typically various components (e.g., buttons, windows, etc.) on the business component 220; second, an Event (Event) for encapsulating specific information of a specific Event occurring on the interface component, which is generally delivered through an Event object if an Event listener needs to acquire information of an Event occurring on the interface component; and thirdly, an Event Listener (Event Listener) for listening to events occurring at the Event source and performing corresponding processing on different events.
In this embodiment, when the user clicks a corresponding event source (e.g., a button, a screen touch point, etc.) in the target service component, the event listener in the target service component listens to the corresponding event and passes the event through to the message distribution component 210.
The transparent transmission refers to only transmitting the event and not processing the event. In this embodiment, the step S120 can be implemented by the following steps:
when the target service component listens for an event, it invokes a broadcast event instruction to pass the event through to the message distribution component 210.
That is, the target business component can pass through a gift panel to the message distribution component 210 by calling a broadcastevent (clickevent) method.
In step S130, when receiving the event, the message distribution component 210 sends a notification message corresponding to the event to each associated service component 220 to notify the corresponding service component 220 to process the event.
Wherein the notification message includes identification information associated with the target business component. In other words, based on the identification information in the notification message, the event source is associated with business logic that processes the event source.
Optionally, in this embodiment, the step S130 may be implemented by:
the message distribution component 210 sends a notification message corresponding to the event to each business component 220 in the aggregate list.
In the present embodiment, since the aggregate list modelList is used to maintain the service components 220 that need to be used currently, all the service components 220 that need to be used currently are included. Thus, as long as a notification message corresponding to the event is sent to each service component 220 in the aggregate list modelist, the target service component may also receive the notification message and then process the event corresponding to the notification message.
When the target service component is no longer needed to be used, the function corresponding to the target service component cannot be used any more as long as the target service component is removed from the aggregate list modelist.
In step S140, each service component 220 that receives the notification message determines whether the notification message includes the identification information associated with each service component, and if so, processes the event corresponding to the notification message.
In this embodiment, each service component 220 in the aggregate list modelList receives the notification message, and after receiving the notification message, each service component 220 detects whether the notification message includes identification information associated with itself, and if so, determines that the notification message should be processed by itself, and performs subsequent processing actions. If not, the notification message may be determined not to belong to its own processing range, and subsequent processing operations may not be performed.
Optionally, in this embodiment, in step S140, the step of processing the event corresponding to the notification message may be implemented by the following sub-steps:
and calling a corresponding functional module to process the event corresponding to the notification message based on the identification information included in the notification message.
And the corresponding functional module refers to a functional module corresponding to the service logic matched with the identification information.
Therefore, by distributing the message distribution component 210, decoupling between the functional modules in the service component 220 is achieved, and if a certain functional module needs to be updated (or uninstalled), only the functional module in the service component 220 needs to be deleted, and no adjustment is needed to be made to other modules or components.
An application scenario of the event processing method provided in this embodiment is given below, and it is assumed that the APP is a live APP, and the target service component is a gift panel in the live APP.
When the gift function needs to be used, the gift panel is loaded into the modelList through the loadModel function, and thus the gift panel will receive the notification message sent by the message distribution component 210. When the gift function is not needed, the unloadModel () method is simply called to remove the gift panel from the modelList, so that the notification message sent by the message distribution component 210 cannot be received by the gift panel, and the user cannot use the gift function any more.
Taking the display and hiding functions of the gift panel as an example, the gift panel is provided with corresponding display buttons and hiding for the user to control the display and hiding of the gift panel. Based on the event processing method provided by the embodiment of the invention, the business logic of displaying and hiding the gift panel is not needed to be realized in the monitoring event of the gift panel, but one-time transparent transmission is carried out in the monitoring event.
That is, when the gift panel monitors that the user clicks the display button (or the hidden button), the event of clicking the display button (or clicking the hidden button) is transmitted to the message distribution component 210, the message distribution component 210 sends a notification message corresponding to the event to each service component 220 in the modelList, and the message is received by the gift panel because the service component 220 of the gift panel is included in the modelList.
When the gift panel receives the notification message, it can be determined that the event corresponding to the notification message should be processed by itself based on the identification information in the notification message, and then it is determined that the function module processing the event corresponding to the notification message is a gift panel display module (or a gift panel hiding module) according to the identification information, and the gift panel display module (or the gift panel hiding module) is invoked to process the event. While other service components 220 in the modelList, except for the gift panel, do not process the notification message.
Therefore, the decoupling among the functional modules in the gift panel can be realized.
In practical applications, a certain service function may require that a plurality of service components 220 cooperate with each other to be implemented, and thus, in this embodiment, the target service component may be one or two or more.
When one target service component is provided, the method provided by the embodiment of the invention can realize the decoupling between the functional modules in the service component 220; when the number of the target service components is two or more, the decoupling between the service components 220 can be realized by adopting the method provided by the embodiment of the invention, thereby improving the development efficiency.
As shown in fig. 3, the embodiment of the present invention further provides a client 200, where the client 200 includes a message distribution component 210, a plurality of business components 220 (only one is shown in fig. 3), and an association module 230.
The association module 230 is configured to associate a target service component with the message distribution component 210, so that the target service component can receive a message sent by the message distribution component 210.
In this embodiment, the description of the association module 230 may specifically refer to the detailed description of the step S110 shown in fig. 2, that is, the step S110 may be executed by the association module 230.
For the functions of the message distribution component 210 and the service components 220, reference is made to the detailed description of the relevant steps in the above.
Optionally, as shown in fig. 4, the client 200 may further include an disassociation module 240.
The disassociation module 240 is configured to remove a specified business component 220 from the aggregated list to disassociate the business component 220 from the message distribution component 210, such that the business component 220 cannot receive the notification message sent by the message distribution component 210.
In this embodiment, the detailed description of the disassociation module 240 may refer to the detailed description of the related steps in the above.
The embodiment of the invention also provides a computer readable storage medium, on which computer instructions are stored, and when the computer instructions are executed, the event processing method provided by the embodiment of the invention is realized.
In summary, the event processing method and the client 200 provided in the embodiments of the present invention associate the target service component with the message distribution component 210, so that the target service component can receive the message sent by the message distribution component 210. The target service component transparently transmits the monitored event to the message distribution component 210, and the message distribution component 210 sends a notification message corresponding to the event to each associated service component 220 when receiving the event, so as to notify the corresponding service component 220 to process the event. Each service component 220 that receives the notification message determines whether the notification message includes the identification information associated with each service component, and if so, processes the event corresponding to the notification message. Through the design, the decoupling of the service component 220 is realized, and the development efficiency is improved.
In the several embodiments provided in the present application, it should be understood that the disclosed client and method may be implemented in other ways. The client embodiments described above are merely illustrative, and the flowcharts and block diagrams in the figures, for example, illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present invention. 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.
In addition, the functional modules in the embodiments of the present invention may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It is 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 phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (9)
1. An event processing method is applied to a client side comprising a message distribution component and a plurality of service components, and comprises the following steps:
associating a target business component with the message distribution component to enable the target business component to receive the message sent by the message distribution component;
when the target business component monitors an event, the event is transmitted to the message distribution component;
when receiving the event, the message distribution component sends a notification message corresponding to the event to each associated service component to notify the corresponding service component to process the event, wherein the notification message comprises identification information associated with the target service component;
each service component receiving the notification message judges whether the notification message comprises identification information associated with each service component, and if the notification message comprises the identification information, an event corresponding to the notification message is processed;
wherein, the step of processing the event corresponding to the notification message comprises:
and calling a corresponding functional module to process the event corresponding to the notification message based on the identification information included in the notification message.
2. The method of claim 1, wherein the message distribution component comprises a predetermined set list;
the step of associating a target business component with the message distribution component includes:
loading a target business component into the aggregate list;
the step of the message distribution component sending the notification message corresponding to the event to each associated business component includes:
the message distribution component sends a notification message corresponding to the event to each business component in the aggregate list.
3. The method of claim 2, further comprising:
and removing the designated business component from the set list to release the association of the business component and the message distribution component, so that the business component cannot receive the notification message sent by the message distribution component.
4. The method according to any one of claims 1 to 3, wherein the step of the target business component transmitting the monitored event to the message distribution component when the target business component monitors the event comprises:
and when the target service component monitors the event, calling a broadcast event instruction to transmit the event to the message distribution component.
5. A client, characterized in that the client comprises a message distribution component, a plurality of service components and an association module;
the association module is used for associating a target business component with the message distribution component so that the target business component can receive the message sent by the message distribution component;
the target business component is used for transmitting the event to the message distribution component in a transparent way when monitoring the event;
the message distribution component is used for sending a notification message corresponding to the event to each associated service component after receiving the event so as to notify the corresponding service component to process the event, wherein the notification message comprises identification information associated with the target service component;
each service component receiving the notification message is used for judging whether the notification message comprises identification information associated with each service component, and if the notification message comprises the identification information, processing an event corresponding to the notification message;
wherein, processing the event corresponding to the notification message includes:
and calling a corresponding functional module to process the event corresponding to the notification message based on the identification information included in the notification message.
6. The client of claim 5, wherein the message distribution component comprises a predetermined set list;
the association module loads the target business component into the aggregate list to associate the target business component with the message distribution component;
and the message distribution component sends a notification message corresponding to the event to each business component in the aggregate list, so that the notification message corresponding to the event is sent to each associated business component.
7. The client of claim 6, further comprising:
and the association releasing module is used for removing the specified business component from the set list so as to release the association between the business component and the message distribution component, so that the business component cannot receive the notification message sent by the message distribution component.
8. The client side according to any one of claims 5 to 7, wherein the target service component, when monitoring an event, passes through the event to the message distribution component by calling a broadcast event instruction.
9. A computer readable storage medium having computer instructions stored thereon, wherein the computer instructions, when executed, implement the method of any of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710890729.4A CN107783849B (en) | 2017-09-27 | 2017-09-27 | Event processing method and client |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710890729.4A CN107783849B (en) | 2017-09-27 | 2017-09-27 | Event processing method and client |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107783849A CN107783849A (en) | 2018-03-09 |
| CN107783849B true CN107783849B (en) | 2021-01-01 |
Family
ID=61434099
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710890729.4A Active CN107783849B (en) | 2017-09-27 | 2017-09-27 | Event processing method and client |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107783849B (en) |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110769018A (en) * | 2018-07-27 | 2020-02-07 | 北京国双科技有限公司 | Message pushing method and device |
| CN109361953B (en) * | 2018-09-18 | 2022-04-08 | 武汉斗鱼网络科技有限公司 | Dynamic distribution method, device, equipment and storage medium of barrage message |
| CN111142982A (en) * | 2018-11-02 | 2020-05-12 | 鸿合科技股份有限公司 | Event execution method and device and electronic equipment |
| CN109767342A (en) * | 2018-12-13 | 2019-05-17 | 中国平安财产保险股份有限公司 | A kind of data processing method, system, terminal and storage medium |
| CN109656536B (en) * | 2018-12-25 | 2022-08-16 | 武汉斗鱼网络科技有限公司 | Push module modularization method and client |
| CN109885334B (en) * | 2018-12-30 | 2022-10-04 | 贝壳技术有限公司 | Version compatible system and message sending and receiving method |
| CN110138574B (en) * | 2019-03-26 | 2021-10-26 | 北京达佳互联信息技术有限公司 | Group management method, device, electronic equipment and readable storage medium |
| CN111768572B (en) * | 2020-01-14 | 2022-09-30 | 北京沃东天骏信息技术有限公司 | Display control method and device for cash register equipment, medium and electronic equipment |
| CN111427710B (en) * | 2020-03-30 | 2022-06-28 | 南京领行科技股份有限公司 | Communication method, device, equipment and storage medium of components in application program |
| CN112015523B (en) * | 2020-08-03 | 2023-09-01 | 北京奇艺世纪科技有限公司 | Event loss prevention method and device, electronic equipment and storage medium |
| CN112084044B (en) * | 2020-08-27 | 2024-02-02 | 腾讯科技（深圳）有限公司 | Event processing method in system and related device |
| CN114764292A (en) * | 2022-04-19 | 2022-07-19 | 润芯微科技(江苏)有限公司 | Method for realizing multi-screen control vehicle-mounted central control screen |
| CN115987673B (en) * | 2022-12-30 | 2023-12-08 | 北京天融信网络安全技术有限公司 | Vulnerability penetration test system, method, device, medium and equipment based on event driving |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1350165A2 (en) * | 2000-07-19 | 2003-10-08 | Opendesign Inc. | Event bus architecture |
| US6785726B1 (en) * | 2000-05-08 | 2004-08-31 | Citrix Systems, Inc. | Method and apparatus for delivering local and remote server events in a similar fashion |
| CN101201755A (en) * | 2007-05-10 | 2008-06-18 | 深圳市同洲电子股份有限公司 | Method, system and equipment for managing software module of digital receiving terminal |
| CN101789938A (en) * | 2010-01-12 | 2010-07-28 | 清华大学 | Agent-based component generation method in reconfigurable software |
| CN104662516A (en) * | 2012-07-27 | 2015-05-27 | 谷歌公司 | Messaging between web applications |
| CN106250246A (en) * | 2016-07-25 | 2016-12-21 | 福建天泉教育科技有限公司 | A kind of method and system of event transmission |
| CN107015851A (en) * | 2016-01-28 | 2017-08-04 | 阿里巴巴集团控股有限公司 | A kind of serviced component management method and system |
-
2017
- 2017-09-27 CN CN201710890729.4A patent/CN107783849B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6785726B1 (en) * | 2000-05-08 | 2004-08-31 | Citrix Systems, Inc. | Method and apparatus for delivering local and remote server events in a similar fashion |
| EP1350165A2 (en) * | 2000-07-19 | 2003-10-08 | Opendesign Inc. | Event bus architecture |
| CN101201755A (en) * | 2007-05-10 | 2008-06-18 | 深圳市同洲电子股份有限公司 | Method, system and equipment for managing software module of digital receiving terminal |
| CN101789938A (en) * | 2010-01-12 | 2010-07-28 | 清华大学 | Agent-based component generation method in reconfigurable software |
| CN104662516A (en) * | 2012-07-27 | 2015-05-27 | 谷歌公司 | Messaging between web applications |
| CN107015851A (en) * | 2016-01-28 | 2017-08-04 | 阿里巴巴集团控股有限公司 | A kind of serviced component management method and system |
| CN106250246A (en) * | 2016-07-25 | 2016-12-21 | 福建天泉教育科技有限公司 | A kind of method and system of event transmission |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107783849A (en) | 2018-03-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107783849B (en) | Event processing method and client | |
| US20200226185A1 (en) | Publishing rest api changes based on subscriber's customized request | |
| US20200201837A1 (en) | Live record invalidation | |
| CN111049705A (en) | Method and device for monitoring distributed storage system | |
| CN110532322B (en) | Operation and maintenance interaction method, system, computer readable storage medium and equipment | |
| CN105490917B (en) | Method and device for realizing sharing in application | |
| CN111258847B (en) | File handle monitoring and analyzing method, device, medium and equipment | |
| CN113779339A (en) | Automatic monitoring and alarming method and system | |
| CN112506587B (en) | API deployment monitoring method, system, electronic device and storage medium | |
| CN111694677A (en) | Message queue management method, device, terminal and computer-readable storage medium | |
| CN112199210A (en) | Data processing method and device based on Internet of things, computer equipment and medium | |
| WO2015067189A1 (en) | Method and apparatus for installing application | |
| CN110912807A (en) | Information prompting method and device, electronic equipment and computer readable storage medium | |
| CN110881224B (en) | Network long connection method, device, equipment and storage medium | |
| CN111240998B (en) | Test case processing method and device | |
| CN110908881B (en) | Buried point data transmitting method and device, electronic equipment and computer readable storage medium | |
| US10419602B2 (en) | Suppressing indications of events in user interfaces | |
| CN112668998B (en) | Flow implementation method, device, system, electronic equipment and readable storage medium | |
| CN110971697B (en) | Redis single instance protection processing method and device, computer equipment and storage medium | |
| CN109936586B (en) | Communication processing method and device | |
| CN114968696A (en) | Index monitoring method, electronic equipment and chip system | |
| CN112199078A (en) | Toast message pushing method and device based on android fragment component and computer equipment | |
| CN110658969B (en) | Picture processing method, device, equipment and storage medium | |
| CN111045723B (en) | Method and device for notifying code change between associated systems | |
| CN110704219A (en) | Hardware fault reporting method and device and computer storage 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 | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20231017 Address after: No. 156 Dongfeng Road, Zhonghe Street, Xiushan Tujia and Miao Autonomous County, Chongqing 409900 Patentee after: Xiushan county xiaocan information technology Co.,Ltd. Address before: 430000 East Lake Development Zone, Wuhan City, Hubei Province, No. 1 Software Park East Road 4.1 Phase B1 Building 11 Building Patentee before: WUHAN DOUYU NETWORK TECHNOLOGY Co.,Ltd. |