On Thu, Sep 3, 2009 at 7:30 AM, Ian Hickson<i...@hixie.ch> wrote: > On Mon, 31 Aug 2009, Mike Shaver wrote: >> >> The multiple server-side processes that end up involved over the course >> of the user's interaction do need to share state with each other, and >> preserving blocking semantics for accessing such state makes the >> programs much simpler to reason about given today's programming >> languages. Is that shared state not what the Global Script Object would >> provide? > > Aren't global script objects supposed to be client-side? I don't see how > they would help with server-side state.
Yeah, I was reasoning by analogy; the global script object would on the client be used as the databases or session state are on the server side. (Especially since LocalStorage isn't available to workers.) Mike