[Encore] forked task stops after a few weeks

[Daniel Jung]

Kevin Jepson wrote:
> Daniel
> I'm curious as to why you used a Fork for this and not just repeated
> suspends? 

Good question. I have a good answer.

This verb is a web-verb, not player-initiated, so the player cannot be 
addressed for printouts. The verb has to RETURN the result (to the 
caller). If I put the return before the suspend, then the suspend will 
never be reached, if I put the return after the suspend, I must wait a 
long time for the result. Putting in a fork allows me to do both: have 
an immediate result returned and the verb repeated after a given time, 
with the same result return all over again.

I could maybe have written the result to a property and have the web 
page (which initiated the task) refresh itself somehow with a box 
displaying the given property. But the fork() seemed more logical, less 
error prone, and cleaner.

- Daniel