That’s exactly the thing: It’s an admin setting which significantly changes the user experience, so there’s all reason to remove it.
It’s not about not overwhelming admins with options – it’s about not enabling them to deactivate something very useful. On Sat, Aug 11, 2012 at 3:43 PM, Thomas Tanghus <[email protected]> wrote: > On Saturday 11 August 2012 14:08 Jan-Christoph Borchardt wrote: >> On Sat, Aug 11, 2012 at 2:03 PM, Jakob Sack <[email protected]> wrote: >> > as far as I know there is no reason for completely disabling background >> > jobs. >> Ah sorry, I phrased it wrong. I didn’t mean »just use AJAX all the >> time and remove the option for cron jobs«, I meant »AJAX is always >> available and has no negative effect, so let’s just not have an option >> to deactivate background jobs«. >> Of course if the server supports it, cron should be used. >> >> TL;DR: Nice, let’s remove the option to deactivate background jobs. > > This is a system admin setting, so I see no reason for removing the option. It > could be set to default to AJAX with the option to change it or disable it. > > Btw Jakob, are the backends made as plugins? I would like to write a fifth > option ;) > > -- > Med venlig hilsen / Best Regards > > Thomas Tanghus > _______________________________________________ > Owncloud mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/owncloud _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
