Neither "end" nor "close" are ever emitted. * HttpServerResponse is a WritableStream which does not emit "end" events. * WritableStreams emit "close" events "when the underlying file descriptor has been closed," which doesn't seem applicable. * HttpServerResponses emit "close" events to indicate "that the underlaying connection was terminated before response.end() was called or able to flush," which is not the case.
That's as far as documentation goes. On Tuesday, July 10, 2012 6:48:00 PM UTC-4, mscdex wrote: > > On Jul 10, 5:25 pm, Domenic Denicola <dome...@domenicdenicola.com> > wrote: > > I am trying to create a mini dashboard for my server that shows number > of > > "unfinished requests." (BTW if there's a better term for that let me > know.) > > I would listen for response's 'close' event. As Roly mentioned, this > should fire for connections that are either closed naturally or closed > due to some error. -- 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
