I understand the intent and benefit of using later to run this in a separate thread. Understanding the thread component, I have a use-case where I'd like to reduce the latency as much as possible (and still do this in R). Is the best/only way to do this to repeatedly call later::run_now()? Is there a minimum interval imposed internally where running run_now() inside of this interval is unlikely to see incoming data?
Ideally it would be nice to have the ability to impose a blocking poll for incoming data.
I understand the intent and benefit of using
laterto run this in a separate thread. Understanding the thread component, I have a use-case where I'd like to reduce the latency as much as possible (and still do this in R). Is the best/only way to do this to repeatedly calllater::run_now()? Is there a minimum interval imposed internally where runningrun_now()inside of this interval is unlikely to see incoming data?Ideally it would be nice to have the ability to impose a blocking poll for incoming data.