24599 2014-02-10 14:42:54 +0000 Don't these task queues depend on the available APIs? E.g. I suppose for file APIs we'll have some kind of "file read task source" and maybe an "IO task source". 2014-04-15 10:20:45 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED WORKSFORME http://www.whatwg.org/specs/web-apps/current-work/#worker-event-loop P3 normal Unsorted 1 contributor ian annevk ian mike contributor oldest_to_newest 100147 0 contributor 2014-02-10 14:42:54 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/workers.html Multipage: http://www.whatwg.org/C#worker-event-loop Complete: http://www.whatwg.org/c#worker-event-loop Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: Don't these task queues depend on the available APIs? E.g. I suppose for file APIs we'll have some kind of "file read task source" and maybe an "IO task source". Posted from: 82.130.78.44 by annevk@annevk.nl User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:30.0) Gecko/20100101 Firefox/30.0 100214 1 ian 2014-02-10 21:41:28 +0000 I don't understand what you are asking here. Can you elaborate? 100274 2 annevk 2014-02-11 13:34:46 +0000 The introductory text seems unnecessarily restrictive: "This event loop has no associated browsing context, and its task queues only have events, callbacks, and networking activity as tasks." I suspect there may be many more kinds of tasks going forward. 100315 3 ian 2014-02-11 19:46:07 +0000 Like what kind of task? 100389 4 annevk 2014-02-12 11:15:46 +0000 File read task. Disk IO task. See comment 0. 100411 5 ian 2014-02-12 17:24:44 +0000 Why would you queue a task to read a file or do disk I/O? That makes no sense. It'd be done in the background, no? (Note that "network activity" tasks are really just callbacks, not network activity. A fetch for a file:// with disk I/O would queue these "network activity" callback tasks.) 100416 6 annevk 2014-02-12 17:42:27 +0000 Right, they would be callbacks that can be used by FileReader to read a blob. That would not go through fetch, but through "blob read" or some such. 100639 7 ian 2014-02-14 22:00:42 +0000 Right. So, a callback. Like the spec says: "... only have events, callbacks, and networking activity as tasks". Network activity is only mentioned because of the weird way "fetch" works, but things like FileReader don't get used for anything but regular callbacks, so they don't need anything special mentioned here. 101158 8 ian 2014-02-21 22:19:30 +0000 I don't know what to do to the spec to fix this. If there's specific specs that queue specific new kinds of tasks that aren't mentioned in the HTML spec, then please let me know. Otherwise, I guess this is WORKSFORME. 102450 9 annevk 2014-03-17 14:20:31 +0000 That's not true. E.g. if you have async XMLHttpRequest that you feed a Blob, it will use the tasks queued by reading the Blob to send that data over the network. No callbacks involved. 102487 10 ian 2014-03-17 19:35:51 +0000 Why would those use tasks at all? 102500 11 annevk 2014-03-17 20:42:19 +0000 What's the alternative? Some kind of English prose that says you do a synchronous read in the background? I guess that could work too... 102597 12 ian 2014-03-18 18:36:48 +0000 If it's just happening in the background, who cares what the timing is. You only need to use tasks when it would otherwise expose author-visible races. 103836 13 ian 2014-04-14 21:44:29 +0000 Anne, I still don't really understand what you want me to do here. 103868 14 annevk 2014-04-15 10:20:45 +0000 I guess it's fine. The current sentence seems overly restrictive, but maybe network is indeed the only special case...