No more music videos with green screens? 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. The Clojure layout is something to seriously consider, and IMHO you do not have to take over full functional style to adept to its sharing immutables by default through atomic references.
PS: the "More examples" links in Readme.md point to https://github.com/xk/private_threads_a_gogo/ On Wed, Mar 7, 2012 at 8:23 PM, Jorge <[email protected]> wrote: > On Nov 16, 2011, at 10:21 PM, Ryan Dahl wrote: >> On Thu, Nov 10, 2011 at 12:59 AM, Jorge <[email protected]> wrote: >>> On 10/11/2011, at 01:18, Jorge wrote: >>>> On 09/11/2011, at 19:49, Jeff Fifield wrote: >>>> >>>>> How is your proposal better/worse/same/different than webworkers or just >>>>> communicating with a pool of worker processes? >>>> >>>> I'm not sure, we'll see. >>> >>> One more thing: >>> >>> The ability to launch a pool of node *processes* (not threads), + the >>> ability to inter communicate them, with a good API that makes it easy (and >>> fast), is at least as important as (if not more than) the need to run an >>> in-process cpu-bound task asynchronously, without blocking the event loop, >>> in the background. >>> >>> The former is being developed by ry and co. (RyCo, SF), it's the .fork() >>> thingy. >>> But the latter is not, and that's what I'm trying to address with this. >>> >>> There's a reason for wanting the latter: if you delegate a long running >>> cpu-bound task to a node worker *process*, you're gonna block its event >>> loop. >>> That means that it will in fact go 'offline' for the duration of the task! >>> Not so with b/g threads. >> >> I'm not sure what you mean about blocking here... >> >>> OTOH, the OS resources such a file descriptors available to a single node >>> process are not unlimited: it's easy to hit the limit if you try e.g. to >>> open 100k files at once. This kind of problems are solved by a pool of >>> (well) interconnected node processes, but not with threads. >> >> >> We're also adding Isolate support for v0.8. We should combine forces. >> Let's talk on IRC. > > Today is the D day, finally: JavaScript threads for Node.js (using v8 > isolates): > > https://github.com/xk/node-threads-a-gogo > > npm install threads_a_gogo > > Special thanks to: Bruno Jouhier and Liam Breck. > > Enjoy! > -- > Jorge. > > -- > 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 -- 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
