Always polling was yesterday...

.. because with taskKS you could embed your process functions and they should be triggered to do a service-call only, if it was necessary (ok - on the starting code you'll need the signal call additionally to trigger the task to do somethink yet).
This should save processors-time if you had a straigt always-poll-in-any-subtask structure in your code; tell me your opinions.
Could also be combined with a message/mail system, e.g. to move events to the processfunctions via a small system - may be a feature for next versions of taskKS.