Re: [whatwg] asynchronous JSON.parse and sending large structured data between threads without compromising responsiveness

2013-08-07 Thread Ian Hickson
On Tue, 6 Aug 2013, Boris Zbarsky wrote: > On 8/6/13 5:58 PM, Ian Hickson wrote: > > > > Parsing is easy to do on a separate worker, because it has no > > dependencies -- you can do it all in isolation. > > Sadly, that may not be the [case]. > > Actual JS implementations have various "thread-lo

Re: [whatwg] asynchronous JSON.parse and sending large structured data between threads without compromising responsiveness

2013-08-06 Thread Boris Zbarsky
On 8/6/13 5:58 PM, Ian Hickson wrote: One could imagine an implementation strategy where the cloning is done on the sending side, or even on a third thread altogether The cloning needs to run to completion (in the sense of capturing an immutable representation) before anyone can change the dat

Re: [whatwg] asynchronous JSON.parse and sending large structured data between threads without compromising responsiveness

2013-08-06 Thread Ian Hickson
On Thu, 7 Mar 2013, j...@mailb.org wrote: > > right now JSON.parse blocks the mainloop, this gets more and more of an > issue as JSON documents get bigger and are also used as serialization > format to communicate with web workers. I think it would make sense to have a Promise-based API for JSON