This got off topic. The question is: How to reliably terminate streams, not leaving memory leaks and possible app crashers behind?
I want a way how to terminate a stream in any state, making it stop doing whatever it was doing, close files it opened, and not throw any more errors that might bubble up and crash the app. Currently, as shown in the code snipped linked in the first post, I'm binding empty functions to error listeners to not cause error bubbling, and than pausing/ending streams hoping it does what I want it to and will be collected by next GC run. That is an equivalent of building a rocket ship with duct tape. God damit node documentation, leaving half the questions unanswered and behaviors undescribed... why is .destroy() method which is present on all streams undocumented? What does it do exactly? Anyone? On Friday, September 27, 2013 10:43:06 AM UTC+2, greelgorke wrote: > > waiting for 'open' is a good way, yes. > > in this specific case there is the check for directory existence, not the > file to write. but sure, waiting for open before piping seams a better > solution. > > Am Freitag, 27. September 2013 10:23:51 UTC+2 schrieb Alex Kocharin: >> >> >> i sugest you to check the dir existence with fs.stat first. It's more >>> reliable and it's a better code style to check explicitly for expeting >>> error states, before it creates a runtime error like ENOENT. >>> >> >> It's actually less reliable because of race conditions. >> >> It doesn't matter very much in this particular case, but checking a temp >> file existence before opening it is a classic "never do that" example. >> >> -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
