On Friday, June 29, 2012 5:23:47 AM UTC-4, mscdex wrote: > > > Your reference for calling req.pause() "useless" is a set of mailing > list posts from early last year and things have improved at least > somewhat since then. Since node 0.7.x (specifically [1]), there > shouldn't be any 'data' events emitted after you call req.pause() for > HTTP requests, not until you call req.resume(). From what I gather > there is still an open issue with piping though. > > Thanks very much for pointing this out; I didn't know we would get this in the 0.8 upgrade. Do you have any more details on the remaining piping issue? Marco, would you recommend calling this new `pause` over using a buffered stream?
> Regarding the sending of TCP NAKs, etc., at this point I think you > shouldn't be worrying about this behavior until you've verified in > production that it is a real limiting factor for your application. > > This was also very helpful advice. Combined with some in-person discussions with Mark Cavage, it turns out I didn't really understand the TCP stuff that was going on, and thought it was much heavier than it really is. Apparently pausing is a really good idea anyway for my scenario. ---- If anyone's at NodeConf and wants to help me work out a good solution over drinks (caffeinated or alcoholic), I'd be super-appreciative. I could also use some help reassuring myself that I won't leak memory with any given approach: it turns out my understanding of garbage collection is pretty fuzzy :/. -- 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
