Very interesting, so could a domain cover an entire request in your typical web application. Basically,giving you the ability to respond to any error that may occur in an async callback, because the domain would be keeping the context of the initial request? That would be a really big win for request based concurrent systems like web apps.
On Feb 10, 8:05 am, Ben Noordhuis <[email protected]> wrote: > On Fri, Feb 10, 2012 at 05:59, Brad Carleton <[email protected]> wrote: > > Currently, async error handling in node is difficult. I know that you > > guys are working hard on domains. Do domains solve some of the > > problems of async error handling and are they similar to an async try/ > > catch? > > Not quite. > > The idea behind domains is that you stuff handles (sockets, timers, > etc.) that are somehow related into a domain. On error (socket > timeout, network outage, whatever), you kill off the domain. Node > magically cleans up for you and your application keeps on trucking. > It's uncaughtException done right. > > The feasibility of domains is still under discussion - there are a lot > of edge cases - but that's the general idea. -- 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
