Alexandre Julliard julliard@winehq.org wrote:
Would starting the service from taskschd.dll when an application calls ITaskService::Connect() be a viable compromise? Of course that would mean that the scheduled tasks will be added to the queue only when the service is running.
If there are scheduled tasks then it's OK for the service to be running always; but as long as there aren't, it should be started on-demand.
So I would implement it like this: the service would be always started on Wine boot, it would then load the xml task definitions and if there is no anything would exit right away. Then the service would be started by taskschd.dll if ITaskService::Connect() can't connect to an existing service instance. Does this sound acceptable?
No, having it start always defeats the whole point. Just mark it auto-start once a task is added.
In 'Try 3' I tried to address all the discussed things, is there anything else that prevents this patch from being accepted?