[dev] [commits] Horde branch master updated. 18a53c7ffc56dd4df59a389b1f366a7089f51df6

[Chuck Hagenbuch]

Quoting Michael M Slusarz <slusarz at horde.org>:

>>> API calls are a bit more difficult.  Example: I have an IMP login  
>>> task to delete sent-mail folders past a certain age.  If I make an  
>>> API call to list folders in IMP, this login task *must* be run  
>>> before returning the list.
>>
>> I'm not sure I follow this argument. API calls are different from  
>> logging in to a service in my opinion; you may need to be  
>> authorized, but it's not the same.
>
> A better argument is that we can no longer use logintasks for  
> upgrade tasks - i.e. the way Maintenance tasks are used in turba  
> and/or kronolith right now.
>
> Maybe add a way to flag certain logintasks as "system" tasks, and  
> only run these logintasks in API calls?

That makes sense. I think a different parent class for system tasks  
would be best because it should be very strict that system tasks  
require no UI and no user intervention. Having that capability, in  
addition to user-focused login tasks, sounds very nice though.

-chuck