On Fri, Oct 19, 2012 at 5:40 PM, anup <[email protected]> wrote: > Thanks Ben for the response. I know this is a bit late and I am sorry for > that. > > The issue was somewhere else. tcpdump nailed it. It was hard to simulate and > when it happened, tcpdump suggested that the packet did reach the other end > of the socket. > > There was nothing special about the code. It was socket.write(). Other > socket related code was scattered all around so I did not know what to add > here. > > However, it is solved now. There is no issue at node. > > Thanks once again.
Glad you got it solved. :-) -- 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
