I have code for both Linux (using an AF_NETLINK socket) and Windows (using NotifyAddrChange) to do this, and I'd love to merge it in, but the external API is an open question.
My current use-case needs to receive change events, but also cancel these events on program exit. To do this, my notifiers spawn threads, send change messages via a crossbeam channel, and have custom Drop impls that wake up a side-channel to cancel the thread.
Async could work here, but async rust scares me a little 😅. Do you have any preferences on what the API should look like?
I just noticed this TODO item in the README.
I have code for both Linux (using an AF_NETLINK socket) and Windows (using NotifyAddrChange) to do this, and I'd love to merge it in, but the external API is an open question.
My current use-case needs to receive change events, but also cancel these events on program exit. To do this, my notifiers spawn threads, send change messages via a crossbeam channel, and have custom
Drop
impls that wake up a side-channel to cancel the thread.Async could work here, but async rust scares me a little 😅. Do you have any preferences on what the API should look like?