Expire Audits
Reported by bahuvrihi | February 12th, 2009 @ 09:56 AM
Currently apps aggregate the results of any tasks that don't have an on_complete block. This plan is good because it prevents the loss of results from tasks that have no termini. However, aggregation isn't always desired (ex in tap-server the default desired action is a render).
App should have a customizable default_on_complete block, by default aggregating the results. With aggregation separated from apps in a fundamental way, there is room for rethinking adding an aggregator by default... consequences:
- results and _results should be left on the aggregator and removed from app
- added bonus of separating this avenue to access other tasks in the app (greater modularity)
Comments and changes to this ticket
-
bahuvrihi February 22nd, 2009 @ 10:05 PM
- Assigned user set to “bahuvrihi”
- State changed from “new” to “resolved”
Added on_complete, but currently aggregator is still in.
-
bahuvrihi February 23rd, 2009 @ 06:44 PM
- State changed from “resolved” to “open”
- Title changed from “App.default_on_complete block” to “Expire Audits”
Continuing this... get the aggregator out. Audits need to be able to expire.
-
bahuvrihi April 17th, 2009 @ 11:56 AM
- State changed from “open” to “resolved”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
A framework for making configurable, file-based tasks and workflows.
bahuvrihi