The library I'm interacting with using node-ffi might crash for certain inputs. When it does, it takes my node process with it. Is there a way to trap this and continue processing other things -- importantly, return a result to the web browser -- or must my node process exit at that point?
I could have a main node process that handles web requests and spawns a second node process to use the library, and monitors whether that second process crashes. But that totally defeats the reason I'm using the library in the first place. I could be using the command line program that ships with the library, but I want to use the library directly, loading and initializing it once at the start of my program, to avoid that overhead, plus the overhead of starting a process, every time I want to use it. -- -- 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.
