Thanks for clarification on this going ahead - disappointing but completely understandable and I'd rather know earlier than later.
The current app I'm working makes heavy use of child_process.fork to call jsdom processes, avoiding high memory use in the core app (jsdom seems to be leaky but because v8-profiler doesn't work with >0.4.x and the author seemed to have abandoned it, it's hard to pinpoint where the issue exactly is) and did anticipate isolates landing in 0.8 - so the design may need to be reconsidered down the line - but at least for now it's not a large user base and the data extracted via jsdom can be cached. If you do have any questions about my use case, please feel free to ping me off-list (the current dev is under NDA so I can't go into detail here). - Tane -- 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
