Async Void Event Handlers: When is it Acceptable?

Async void event handling procedure: Weighing the advantages and disadvantages

Usually, asynchronous Void method (Fire-And-FORGET) is considered a bad practice due to lack of error treatment and hanging task tracking mechanism. However, the guidance principles are slightly different for the processing procedures for asynchronous events.

Use async void in the event processing program: exception

In contrast to the general suggestion, using Async Void in event processing procedures is considered acceptable. This exception is derived from the nature of event handling:

Event processing is synchronized.
• The event is triggered simultaneously, which is different from asynchronous tasks. The duration of the event processing procedure is short.
Event processing procedures usually perform short -term operations, thereby reducing the possibility of abnormalities and unprocessed tasks.
• The potential issues that need to be paid attention to

Although the use of Async Void in the event processing program is acceptable, it is necessary to pay attention to the following potential problems:

Reading the problem:

Event processing procedures may be called multiple times, resulting in potential competition conditions.

• Task tracking: Asynchronous tasks may take some time to complete. For the purpose of testing and debugging, the asynchronous logic is decomposed so that it is easier to track and cancel (if necessary), it will be very helpful.
• Unit testing suggestions For unit tests, consider extracting asynchronous logic from the individual method from the event processing program, as shown below:

This method allows the easier to test and eliminate asynchronous tasks in the event processing procedure without sacrificing the convenience of using Async Void.

The above is the detailed content of Async Void Event Handlers: When is it Acceptable?. For more information, please follow other related articles on the PHP Chinese website!