> > The sender is suspended until the receiver returns.
> And what happens to the receiver? Is the script currently
> running in the receiver context interrupted?
The send function checks the type of its argument. It then checks for the
existence of the receive function. If it exists, it calls
On Wed, 01 Nov 2006 03:01:29 +0600, Douglas Crockford <[EMAIL PROTECTED]> wrote:
>> You need to define precisely what happens in the context of the receiver
>> when it handles a message. Does script processing suspend for that time?
>> Or does it run in parallel to handling the message?
> The sen
On Tue, 31 Oct 2006, Douglas Crockford wrote:
> > > >
> > > > The sender is suspended until the receiver returns.
> >
> > As a quick note, in general we're trying to get away from synchronous
> > scripting. It causes too many problems, especially in browsers written
> > around a single UI thread
> > The sender is suspended until the receiver returns.
> As a quick note, in general we're trying to get away from synchronous
> scripting. It causes too many problems, especially in browsers written
> around a single UI thread on which JS runs. Several APIs are having to be
> grandfathered in
On Tue, 31 Oct 2006, Douglas Crockford wrote:
>
> > You need to define precisely what happens in the context of the
> > receiver when it handles a message. Does script processing suspend for
> > that time? Or does it run in parallel to handling the message?
>
> The sender is suspended until the
> You need to define precisely what happens in the context of the receiver
> when it handles a message. Does script processing suspend for that time?
> Or does it run in parallel to handling the message?
The sender is suspended until the receiver returns.
On Tue, 31 Oct 2006 22:45:53 +0600, Douglas Crockford
<[EMAIL PROTECTED]> wrote:
JSON is a safe subset of JavaScript. It is meaningful in a JavaScsript
context (which is where we currently are). If we ever have a
multilingual future (and I hope that we do), JSON has demonstrated
amazing i
> > It requires no changes to JavaScript and a small, incremental change to
> > HTML.
> > The proposal is here: http://json.org/module.html
> What you propose looks very similar to the Cross-document messaging already
> included into the current draft:
> http://whatwg.org/specs/web-apps/current-
On Tue, 31 Oct 2006 06:04:40 +0600, Douglas Crockford <[EMAIL PROTECTED]> wrote:
> I have been looking at the mashup problem. All scripts run with the authority
> of the base page, so mashups are not indicated for any application containing
> private data or managing a private connection. That is
I have been looking at the mashup problem. All scripts run with the authority
of the base page, so mashups are not indicated for any application containing
private data or managing a private connection. That is extremely limiting. Even
worse, it turns out that rich media ads are mashups.
I had
10 matches
Mail list logo
