and 0.8.17 is what I yam... On Thursday, February 7, 2013 7:26:39 PM UTC-5, am_p1 wrote: > > So most of the time request.abort from inside setTimeout drives only the > request error callback and gets "socket hang up". No problem and I call my > routine again recursively to reconnect to the server in the big sky. Works > great. > > But some of the time request.abort from inside setTimeout drives response > close followed by response end (and never request error), and I have an > incomplete packet at that point, which causes the DB2 XML parser all kinds > of grief. However, the doc says: > 'close' can fire after 'end', but not vice versa. > > And I believe I'm relating the sequence correctly (always iffy with all > this asynchronicity going on) because I'm time stamping everything down to > the microsecond. > > No problem and I think I can code around this but I just wanted to mention > this to the node gods that be in case they want to tell me how messed up my > code is!! > > Thanks!! >
-- -- 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 --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
