0 views collected around this technical thread.
The article explains Locust's event system, detailing common events such as init, test_start, test_stop, request_success, request_failure, quitting, worker_report, and hatch_complete, and provides Python code examples for attaching listeners to customize load‑testing behavior.
This article explores how Taro leverages C++ and the Harmony C‑API to build a high‑performance, cross‑language event system that unifies event handling across C++, ArkTS, and JavaScript, detailing architecture, event center implementation, node event processing, and future enhancements.
This article explains how Taro leverages C++ and the HarmonyOS C‑API to build a high‑performance, multi‑language event system that bridges ArkTS, JavaScript and native components, detailing architecture considerations, implementation details, and future directions for improving cross‑language event handling.
This article explains how Taro leverages C‑API to move runtime logic to C++ and builds a cross‑language event system that unifies ArkTS, JavaScript and C++ on Harmony OS, improving rendering performance, lifecycle management, and developer productivity.
This article explains how React registers event listeners on the root, extracts events from the fiber tree, synthesizes cross‑browser synthetic events, accumulates callbacks, and finally dispatches them, illustrating each step with code examples and diagrams.
React’s synthetic event system wraps native browser events into reusable SyntheticEvent objects, uses a delegated single listener per event type, maps event names through registration modules and plugins, pools event instances, and simulates capture and bubble phases across the fiber tree, with key changes in React 17.