Changes for version 0.14
- An inherited loop's kernel objects are now off-limits to the io and timer watch paths, not just to free. On Linux an epoll instance is a SHARED kernel object across fork - the fd is duplicated but both processes' epoll_ctl calls edit the same interest list - so a forked child that "cleaned up" watchers on a loop it merely inherited was silently deregistering its PARENT's fds.
Modules
an event-loop PSGI server
epoll readiness backend for Hyperman::Loop
io_uring backend for Hyperman::Loop
kqueue readiness backend for Hyperman::Loop
portable poll(2) backend for Hyperman::Loop
a fast, native, Future-compatible async result
the per-worker event loop
Plack/PSGI adapter for the Hyperman server