Upstart 1.0 Design discussion

[Matthias Urlichs]

On Mon, 2009-09-14 at 09:58 -0400, Casey Dahlin wrote:
> From the user perspective, events still behave exactly the same way.
> Inside of Upstart, events no longer block, but the way jobs respond to
> them has been altered such that they appear to.
> 
How do you propose to find event loops with your design?

In the original, it's quite easy -- if you try to change a locked state,
you obviously have a problem. If the 'lock' is represented implicitly
by a stack-of-things-to-do, what would prevent that stack from growing
boundlessly?