I have  dirt simple TCP client/server setup to pass messages between two of 
my apps.  I have a handler on the client that keeps track of disconnects 
and automatically reconnects when that happens.  For some reason the client 
fires the "close" event about every second.  The server doesn't report the 
disconnect but the client seems to think it's not connected.  What's really 
odd is that the message traffic between the two doesn't seem to be affected 
by this and seems to flow normally.

Node version 0.10.31 running on mac 

Anyone have any ideas what might be causing this strange behavior?

I wouldn't mind the events being fired other than when logging is enabled 
it spams my logs up pretty badly.

Thanks,

Noah

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/fc43f49d-5465-4e8f-ba82-3b1113a83cfc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to