prosody.git - unofficial mirror of the prosody mercurial project

	Commit message (Collapse)	Author	Age	Files	Lines
*	MUC: Add Occupant API methods to Teal spec	Kim Alvefur	2023-02-20	1	-0/+6
\|
*	MUC: Add Teal description of muc.lib functions	Kim Alvefur	2023-02-20	1	-0/+9
\|
*	MUC: Start on a Teal description of MUC rooms	Kim Alvefur	2023-02-20	1	-0/+163
\| \| \| \|	Started as part of a documentation project for the MUC API
*	mod_cron: Remove difference between teal version	Kim Alvefur	2022-05-15	1	-1/+1
\| \| \| \| \|	This previously was considered an error because the module API Teal spec did not document a return value from module:add_timer()
*	util.async: Add Teal description file	Kim Alvefur	2022-05-08	1	-1/+1
\|
*	mod_cron: Fix recording last task run time #1751	Kim Alvefur	2022-05-05	1	-0/+1
\| \| \| \| \| \| \|	The type checks, they do nothing! Observed: Tasks that were supposed to run weekly or daily were running each hour.
*	mod_cron: Allow for a small amount of timer drift	Kim Alvefur	2022-01-15	1	-1/+1
\| \| \| \| \| \| \| \| \|	If the timer activates a bit early then a task might be just a few seconds short of being allowed to run. This would run such a task rather than wait another hour. The value 0.5% chosen so that a weekly task does not run an entire hour earlier than last time.
*	mod_cron: Add a 'weekly' job frequency	Kim Alvefur	2021-12-03	1	-1/+2
\|
*	mod_cron: Initialize timestamp of new tasks to start of period	Kim Alvefur	2021-12-03	1	-3/+3
\| \| \| \| \|	Makes it more generic so new periods (e.g. weekly etc) can be added easily.
*	mod_cron: Follow convention of imports at the top	Kim Alvefur	2021-12-03	1	-1/+2
\|
*	mod_cron: Initialize daily tasks so they run around midnight UTC	Kim Alvefur	2021-12-03	1	-0/+5
\| \| \| \| \| \|	Eventually the goal is to have daily tasks run while there is little activity, but that will vary with the server and the usage patterns of its users. This is a start anyway.
*	mod_cron: Initial commit of periodic task runner	Kim Alvefur	2021-11-21	1	-0/+98
	A number of modules now have periodic tasks that need to run, e.g. for cleaning out old messages or files. This has highlighted a need for coordinating and optimizing scheduling of such tasks.