Jörg F. Wittenberger
2018-11-24 20:59:08 UTC
Hi all,
I packages a new new: simple-timer
https://raw.githubusercontent.com/0-8-15/simple-timer/master/simple-timer.release-info
This is intended as the one-stop shopping for low level plumping of the
background threads every other egg needs to put at the core's timeout
queue. (Either because it needs roughly correct time signals or evade false
deadlock detection.)
I hope this could help with is the hell of reasoning about the timeout
queue in an application using several such eggs at the same time: At least
the boring timeouts are under a single umbrella.
Right now it is just the code the `forcible` egg uses under the hood so
far. (Which would be the first candidate to switch. ;-)
Best Regards
/Jörg
I packages a new new: simple-timer
https://raw.githubusercontent.com/0-8-15/simple-timer/master/simple-timer.release-info
This is intended as the one-stop shopping for low level plumping of the
background threads every other egg needs to put at the core's timeout
queue. (Either because it needs roughly correct time signals or evade false
deadlock detection.)
I hope this could help with is the hell of reasoning about the timeout
queue in an application using several such eggs at the same time: At least
the boring timeouts are under a single umbrella.
Right now it is just the code the `forcible` egg uses under the hood so
far. (Which would be the first candidate to switch. ;-)
Best Regards
/Jörg