On Fri, Nov 30, 2012 at 6:13 PM, Isaac Schlueter <[email protected]> wrote:
> The problem is that we create quite a lot of tick callbacks and > EventEmitters and handles, and the list of things gets pretty big. > Doing that for every request is just too expensive, for the edge case > where one of them blows up. > > It might be worthwhile to loop through the process._getActiveHandles() > and process._getActiveRequests() lists and see if any of them are > referring to the disposed domain, and if so... what? The same > heuristics that don't inspire confidence now? > I agree that wouldn't be an improvement. Maybe we need some generic way to kill any HandleWrap or ReqWrap, and > a generic destroy() function that everything in Node with a ._handle > member will respond to? > Yeah, a standard interface would be very helpful. If an I/O action has a strategy for cleaning up after itself, expose it as destroy(), and assume it could be discarded if no destructor is available? This would also be useful for doing a more controlled shutdown of a process if there were either a shutdown call or process._activeHandles were turned into a documented / supported call. I think maybe we're getting to somewhere useful in this conversation. How much of Node core would a change like this touch? Socket, fs, http, stream, EventEmitter, timers...? F -- 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
