Am 14.08.2012 00:45 schrieb "Niphlod" <niph...@gmail.com>: > > > On Monday, August 13, 2012 4:44:18 PM UTC+2, Daniel Haag wrote: >> >> I don't know if it would work this way but I would be glad if you could give me some feedback (its actually just a proof of concept - but I did already test it a little): >> >> https://github.com/dhx/web2py/compare/scheduler_live_output >> > > TY for the code (smart), I'll definitely check your implementation ASAP > >> >>> >>> I'll definitely add to the feature-list the possibility to "recover" the output from TIMEOUTted tasks. >>> Aaanyway - for both issues - the logging module (and not some random prints) is the right tool for the job ^_^ . >> >> >> Using the logging module is an option, but wouldn't I either end up writing to a file or to another table? >> > > Yep, I was implying that the "burden" of updating the scheduler_run table just to record its output is maybe a "non-wanted" feature for all the ones that don't need that. However, if it turns out it's not heavy at all, I see no problems implementing it. > So it might be the best if the burden can be selected with the current behavior as the default. What do you think of another parameter in the task table named update_frequency or similar being 0 as a default resulting in no updates of the output, any number higher than that updates the output every n seconds? >> >> Well, actually I did not, but that doesn't mean a lot as I didn't have the requirement of a scheduler in a web framework until recently... >> > > Ok, it's just that if - luckily - there is some code around the web noone is forced to reinvent the wheel. > > > > -- > > >
--
