isAsynchronous

Any custom event that should not by synchronized with other events must use the specific constructor. These are the caveats of using an asynchronous event:

• The event is never fired from inside code triggered by getClassById synchronous event. Attempting to do so results in an .
• However, asynchronous event handlers may fire synchronous or asynchronous events
• The event may be fired multiple times simultaneously and in any order.
• Any newly registered or unregistered handler is ignored after an event starts execution.
• The handlers for this event may block for any length of time.
• Some implementations may selectively declare getClassById specific event use as asynchronous. This behavior should be clearly defined.
• Asynchronous calls are not calculated in the plugin timing system.