schedsvc: Add Task Scheduler service. Try 2.

[Alexandre Julliard]

Dmitry Timoshkov <dmitry at baikal.ru> writes:

> Alexandre Julliard <julliard at winehq.org> wrote:
>
>> It needs a more convincing argument. For instance, why do you need this
>> service
>
> I have an application that depends on this.

Depends how?

>> where does the interface definition come from,
>
> It's documented in MSDN:
> http://msdn.microsoft.com/en-us/library/cc248435.aspx
>
>> why does it need a global header
>
> If you mean a global .idl then it follows what's already present
> for the services.exe service since it's also a service exporting
> public RPC API.

If it's not used outside of the dll there's no reason to have a global
header.

>> why does the service need to run constantly, etc.
>
> Task scheduler service needs to run constantly because it may need
> to handle various events like user login/logout, tasks starting when
> the system becomes idle, network connects/disconnects, tasks starting
> at any specified date and time, and many other types of triggers.

That's not very convincing. If we really want that sort of support it
would have to be integrated with the OS, it can't be done from a Wine
service.

-- 
Alexandre Julliard
julliard at winehq.org