>> - Can I use Buffers in the child, and can I pass them between isolates? > > Not yet...
It would be nice if there would be an API that stored the PID of the thread the buffer currently "belongs" to, this would make it more fool-proof. >> IMHO it should be possible to share deeply frozen structures without >> having to serialize/deserialize and store the pointer to them into a >> container that guarentees atomicness. > > Yeah, perhaps with proxies, and (hopefully) not necessarily frozen. I understand the approach its up to the next layer to decide which access mechanism to apply. My opinion on this is, the bad reputation threads have is to going the semaphore way, which was long (and still is?) the propsed standard to approach multithreads on working on the same datastructure. However, deeply frozen data structures with atomic references are much easer to get right, or harder to break. They sound less efficient rebuilding a whole tree everytime you change a little thing, but in practice it isn't that dramatic. Its not Javascript strong point, but immutable datastructures also open all kind of new possibilities to optimiziation. Also the current Moores Law gives us more Cores and more Memory, but hardly more linear CPU speed, so it also runs well with hardware development to go for algorithms who don't mind too much to use memory. To cut a long story short, please make it easy for the user to go the immutables/atomic route if s/he decides so. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
