In a browser, postMessage send and receive was always intended to create a synchronization edge in the same way a write-read pair is. http://tc39.github.io/ecmascript_sharedmem/shmem.html#WebBrowserEmbedding
Not sure where this prose ended up when the spec was transfered to the es262 document. --lars On Mon, Sep 24, 2018 at 10:45 AM, T.J. Crowder < [email protected]> wrote: > On Mon, Sep 24, 2018 at 8:42 AM kai zhu > <[email protected]> wrote: > > hi T.J., i'm not a sql-expert, but the big-picture ux-problem you have > > with memory-consistency might be solved by ... > > Thanks, but this isn't a UX or SQL issue; my goal here is to develop a > solid understanding of the JavaScript memory model in regards multiple > threads and shared memory. In particular, whether there is a per-thread CPU > or VM caching issue and, if so, what to do to ensure correctness (other > than using `Atomics.load` for each and every read, which would be silly and > -- from Lars T. Hansen's Mandlebrot example -- clearly isn't necessary). I > have a good understanding of these issues in other environments and want to > bring my understanding of them in the JS environment up-to-scratch. > > -- T.J. Crowder > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
