I've heard that generators helps to catch errors but didn't seen any good explanation how to do that, if anyone knows such an article please post link here
On Wednesday, 15 January 2014 07:48:38 UTC+4, Alexey Petrushin wrote: > > +1 for Fibers > > On Wednesday, 15 January 2014 00:28:52 UTC+4, Gregg Caines wrote: >> >> Hey all... I'm wondering if anyone can point me to the current >> best-practice for isolating requests in a web app. In general I'm trying >> to solve the problem of keeping the server running despite bad code in a >> particular request. Are domains my only shot? Do they completely solve >> it? Does anyone have existing code? >> >> I'm on a somewhat large team, working on a somewhat large codebase, and >> until now I've been just logging restarts and combing logs for these types >> of errors, then fixing them (which I'll always do), but I'm starting to >> feel a bit silly with PHP having solved this 10 years ago. ;) When a bug >> does get through, it would be nice to not lose the whole server and the >> possible 10,000+ customer requests attached to it, while I scramble to fix >> it. >> >> Thanks for any ideas or pointers! >> >> G >> > -- -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com 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 nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
