W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2009

[whatwg] Global Script proposal.

From: Mike Shaver <mike.shaver@gmail.com>
Date: Thu, 3 Sep 2009 12:13:30 -0400
Message-ID: <cc092ba00909030913s432b0b2cwf4f5b3687575f76e@mail.gmail.com>
On Thu, Sep 3, 2009 at 7:30 AM, Ian Hickson<ian at 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
Received on Thursday, 3 September 2009 09:13:30 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:52 UTC