Open markusschlegel opened 5 years ago
Each timeout command currently spawns a new (waiting) thread. We can implement a single reactor event loop that handles all timeouts.
I commited a change that uses a ScheduledExecutorService for both delayed and non-delayed task. So this is maybe obsolete?
Each timeout command currently spawns a new (waiting) thread. We can implement a single reactor event loop that handles all timeouts.