mirror of
https://github.com/servo/servo.git
synced 2025-07-29 02:00:23 +01:00
2de5407cda
Ordering guarantees for timers This is an rough solution to the issue described in #3396. XHRs still do their own thing and an overall clean up is in order. Before I do that, though, I'd really like someone to sign off on the overall idea. There's one major difference to what jdm layed out #3396: The timers remain with the window/worker and only the earliest expiring one is coordinated with the dedicated timer thread. That means both the timer thread and the window/worker have to keep track of which timer expires next, which feels a bit wonky. However, the upshot is that there's no need for communication with the timer thread when a pipeline is frozen, thawed or dropped. Most relvant parts are - the [`TimerScheduler`]( |
||
|---|---|---|
| .. | ||
| dom | ||
| parse | ||
| build.rs | ||
| Cargo.toml | ||
| clipboard_provider.rs | ||
| cors.rs | ||
| devtools.rs | ||
| document_loader.rs | ||
| layout_interface.rs | ||
| lib.rs | ||
| makefile.cargo | ||
| mem.rs | ||
| network_listener.rs | ||
| page.rs | ||
| script_task.rs | ||
| textinput.rs | ||
| timers.rs | ||
| webdriver_handlers.rs | ||
