On Jun 26, 2007, at 5:07 PM, Robert Brewer 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 > > I don't see why it should be limited by that. The primary use case is > anywhere site components and application components are interacting, > that could benefit from a shared understanding (and control) of the > state of the site. To me, that requires a common set of messages, but > the transport mechanism for those messages should be flexible so that > it's useful in both multithread and multiprocess architectures.
Thank you. I see. This is a little too abstract for me to get my brain around, but I'll continue listening and maybe I'll get religion. ;-) - C _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
