[question] Future task vs periodical clock ?
Posted: Fri Apr 23, 2010 7:46 am
Another question i have. I was using tasks that execute in future for features ingame. But currently , im having lots of staff in my code and i need to schedule many tasks in future. In general, i got tasks being scheduled every 10 mins or so. I was thinking, instead of scheduling every 10 mins a different task for each different feature, could i use a task as a clock that is scheduled at fixed rate every 20-30 seconds ? The Task is not heavy, it justs itterates in all the features to check if it is time to take some actions in each one of them.
Whats the most efficient and professional solution between them ? Incase it is scheduling at future for every feature/event ( which is the way L2Jserver does it as i see ) , is it "THAT" bad if i use a task as a clock and tick it with 20 secs period ?
Whats the most efficient and professional solution between them ? Incase it is scheduling at future for every feature/event ( which is the way L2Jserver does it as i see ) , is it "THAT" bad if i use a task as a clock and tick it with 20 secs period ?