+1
Niphold has done an excellent job with the scheduler.
On Monday, 6 August 2012 23:32:58 UTC-5, Michael Toomim wrote:
>
> Thanks for the great work on the scheduler niphlod!
>
> On Wednesday, August 1, 2012 1:19:48 PM UTC-7, Niphlod wrote:
>>
>> The consideration behind that is that if your fun
Thanks for the great work on the scheduler niphlod!
On Wednesday, August 1, 2012 1:19:48 PM UTC-7, Niphlod wrote:
>
> The consideration behind that is that if your function doesn't return
> anything, you don't need the results. Backward compatibility is quite
> broken in that sense (but schedule
On 08/01/2012 01:19 PM, Niphlod wrote:
> The consideration behind that is that if your function doesn't return
> anything, you don't need the results. Backward compatibility is quite
> broken in that sense (but scheduler is still marked as experimental).
> If the function returns something, the sch
The consideration behind that is that if your function doesn't return
anything, you don't need the results. Backward compatibility is quite
broken in that sense (but scheduler is still marked as experimental).
If the function returns something, the scheduler_run record is preserved
(unless the d
On 08/01/2012 12:49 PM, Niphlod wrote:
> Happy to see someone noticing actual improvements :P
> If you need any further explanations / tips&tricks, just ask.
>
> PS: another italian added to web2py-users ;)
Thanks :)
just some considerations though.
I noticed that now in scheduler_run all the C
Happy to see someone noticing actual improvements :P
If you need any further explanations / tips&tricks, just ask.
PS: another italian added to web2py-users ;)
--
On 08/01/2012 11:52 AM, Niphlod wrote:
> you're using the "old" scheduler. the new one operates on a totally
> different logic and it was coded with scalability in mind.
> you can find the relevant code in trunk, the gluon/scheduler.py file is
> what are you looking for.
Updated to trunk and work
you're using the "old" scheduler. the new one operates on a totally
different logic and it was coded with scalability in mind.
you can find the relevant code in trunk, the gluon/scheduler.py file is
what are you looking for.
PS: there is an app to show off the new scheduler behaviour (and shortc
On Wednesday, 1 August 2012 01:36:51 UTC+10, Niphlod wrote:
>
> uhm. try the trunk version remains a valid point.
> Anyway, are you aware that results are json encoded (so to read back them
> into python dictionary you have to do simplejson.loads(results)) ?
>
Wasn't. Thanks.
And will try the
uhm. try the trunk version remains a valid point.
Anyway, are you aware that results are json encoded (so to read back them
into python dictionary you have to do simplejson.loads(results)) ?
Il giorno martedì 31 luglio 2012 13:11:32 UTC+2, Tim Richardson ha scritto:
>
> My scheduled task returns
Thry the trunk version. schedules has changed a lot since last stable.
On Tuesday, 31 July 2012 06:11:32 UTC-5, Tim Richardson wrote:
>
> My scheduled task returns a dictionary which is serialized and stored in
> the scheduler_run table in the result column.
> The dictionary is actually a diction
11 matches
Mail list logo
