ExecutableQueue rounds
Reported by bahuvrihi | January 25th, 2009 @ 06:06 PM
ExecutableQueue should be able to store rounds that effectively get appended when the current round expires. This will more closely emulate schema and solve some problems in Server.
Comments and changes to this ticket
-
bahuvrihi February 11th, 2009 @ 05:06 PM
This is also required to prevent a stop/start cycle for rounds. See http://bahuvrihi.lighthouseapp.c...
-
bahuvrihi February 11th, 2009 @ 08:13 PM
- State changed from “new” to “resolved”
- Assigned user set to “bahuvrihi”
(from [3837fe81322fcd2222fb76c628c3604f2c3fcd32]) added rounds to ExecutableQueue and fixed stop bug [#140 state:resolved responsible:bahuvrihi] [#148 state:resolved responsible:bahuvrihi] http://github.com/bahuvrihi/tap/...
-
bahuvrihi February 16th, 2009 @ 10:30 AM
- State changed from “resolved” to “open”
ExecutableQueue doesn't handle rounds cleanly. It will likely be best to introduce a RoundsQueue, or similar, to track rounds. Maybe even add this at the app level (app.rounds, providing an array of ExecutableQueues).
-
bahuvrihi May 25th, 2009 @ 12:12 PM
- State changed from “open” to “invalid”
ExecutableQueue no longer supports rounds.
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.
People watching this ticket
bahuvrihi
Referenced by
-
140
ExecutableQueue rounds
(from [3837fe81322fcd2222fb76c628c3604f2c3fcd32]) added r...
-
148
Exe.run flubs stop/terminate
(from [3837fe81322fcd2222fb76c628c3604f2c3fcd32]) added r...