Quantcast
Channel: Appcelerator Developer Center Q&A Unanswered Questions 20
Viewing all articles
Browse latest Browse all 8068

socket.io for Node.ACS debug messages and general concept

$
0
0

Hi, I am using socket.io for my Node.ACS. I am always seeing log messages like:

debug: emitting heartbeat for client rHhJdLLqk4eLhMlcyC9y debug: websocket writing 2:: debug: set heartbeat timeout for client rHhJdLLqk4eLhMlcyC9y info: transport end (socket end) debug: set close timeout for client rHhJdLLqk4eLhMlcyC9y debug: cleared close timeout for client rHhJdLLqk4eLhMlcyC9y debug: cleared heartbeat timeout for client rHhJdLLqk4eLhMlcyC9y debug: discarding transport

How can I turn off debug messages?

Another question about general concept: I have a game where the clients have 48 h to send their game results. Each time when they connect to the server I am storing their socket variable. When I want to send something to all clients I iterate the socket list. If someone is not connected any more then sending will fail but this does not matter for me. Do I need heartbeats for my concept? Can I turn them off?

Alex


Viewing all articles
Browse latest Browse all 8068

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>