On 28/06/07, Robert Brewer <[EMAIL PROTECTED]> wrote:
> Phillip J. Eby wrote:
> > Meanwhile, if you get a start call, you must be starting, right?
> > So why worry about the state? It'd be simpler to just use
> > "before/during/after" messages the way Twisted does. Your "block"
> > example could
Chris McDonough wrote:
> I think I'm mostly confused by the name "process bus" because it
> seems like the primary use case for something like this is where all
> of the applications share the same process space and are all written
> in Python. Am I right? If so, maybe a different name is i
Phillip J. Eby wrote:
> Meanwhile, if you get a start call, you must be starting, right?
> So why worry about the state? It'd be simpler to just use
> "before/during/after" messages the way Twisted does. Your "block"
> example could be replaced by waiting for the "after" message of the
> desir