Plus, it would be interesting to know the motivation behind this use case and what scenario it was envisioned for. One thing that comes to mind is efficiency since every request will not have to have a handle to a function. However, apart from the most trivial of use-cases, do you think that passing a handle to the request (and/or) response objects would make this handler generally more useful?
On Friday, August 31, 2012 9:38:05 AM UTC-4, Ben Noordhuis wrote: > > On Fri, Aug 31, 2012 at 3:02 PM, dhruvbird <dhru...@gmail.com<javascript:>> > wrote: > > So is this like a place where _every_ accepted connection's error is > > propagated (in case there is an error on the accepted connection)? > > > > Also, what are the semantics? I mean does the error get propagated > > irrespective of the fact that it might be handled as an 'error' event on > the > > specific 'req' (readablestream) object? > > Yes and yes. > -- 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