Currently the callbacks are not async procedures. This means that if you want to listen to messages and publish messages in response to certain events you need to either use waitFor or add a separate queue system to serve messages from a looping async task. It would be nice to have an overload of subscribe which took a async callback to avoid this. The callback could simply be called with asyncCheck so it wouldn't hang the loop.
Currently the callbacks are not async procedures. This means that if you want to listen to messages and publish messages in response to certain events you need to either use
waitForor add a separate queue system to serve messages from a looping async task. It would be nice to have an overload ofsubscribewhich took aasynccallback to avoid this. The callback could simply be called withasyncCheckso it wouldn't hang the loop.