More flexibility in the ECMAScript part?

David Bruant bruant.d at gmail.com
Thu Apr 18 06:11:39 PDT 2013


Le 18/04/2013 14:59, Jorge a écrit :
> On 18/04/2013, at 14:40, David Bruant wrote:
>
>> I believe the ES spec should provide the primitives of what type of interaction with the message queue is allowed and what isn't. This set of primitives would obviously contain all the interactions allowed today by HTML5.
>>
>> For now, I'm aware of only these types of interactions:
>> 1) add a message to the queue LIFO-style (which is the default?)
> This isn't neccessary,
>
>> 2) add a message to the queue FIFO-style also known as "add for the next turn"
> This is the only one needed,
If you only have this one, then you can end up in situations where user 
inputs are never processed. The 1) is necessary. I assume some 
re-ordering policies/primitives might be necessary too.

>> 3) remove a message (clearTimeout which cancels a message added via a setTimeout message).
> and this has nothing to do with the events queue.
Can you develop your 3 answers, please? Throwing agreement/disagreement 
without providing reasons doesn't help the debate to move forward.
Timeouts do interact with the event loop at least in the WHATWG spec 
(see step 10 of [1] as an example)

David

[1] 
http://www.whatwg.org/specs/web-apps/current-work/multipage/timers.html#dom-windowtimers-settimeout


More information about the es-discuss mailing list