[dev] [commits] Horde branch imp_6_1 updated. d6b64567a2a42f722b042bd63024919f8f7c95ec
Michael M Slusarz
slusarz at horde.org
Tue Feb 26 00:26:29 UTC 2013
Quoting Jan Schneider <jan at horde.org>:
> If possible you should still check if you could turn the tasks into
> independent Horde_Queue tasks though.
How come? As long as the Horde_ShutdownRunner instance is guaranteed
to run in the Horde environment on the current page, what does it
matter? (The ShutdownRunner would never use something like Db storage
because that simply doesn't make any sense).
It is much more useful to be able to define a shutdown task without
regard to what's *in* the shutdown task - in other words, to allow the
shutdown task to be able to altered in the future without worrying
about any state being passed to the task.
I understand that the ShutdownRunner doesn't do much right now, but I
could see in the future adding something like priority queueing - so
that shutdown tasks that MUST happen are run first in case a later
queue task crashes the system and prevents the critical tasks from
running.
michael
___________________________________
Michael Slusarz [slusarz at horde.org]
More information about the dev
mailing list