On 12/03/2012 04:36 PM, Henrik Nordström wrote: > mån 2012-12-03 klockan 15:53 -0700 skrev Alex Rousskov: >> We just need to make sure that heavy events (certain timed events and >> signals) interrupt the sawActivity loop. This will fix the issue you are >> facing without introducing new problems. > > Another question on this.. how to fit the concept of heavy with the goal > of using AsyncCalls?
A heavy event acn be viewed as an "until after comm I/O" delay. I am not sure adding delays to async calls is a good idea. Delays probably belong to the eventAdd() API (unlike events with zero delay that legacy code is probably still using to simulate async calls). HTH, Alex.