server code would be nice. Am Donnerstag, 15. November 2012 10:56:30 UTC+1 schrieb greeka: > > I have TCP server written in NodeJS and clients on flash. The > communications between clients and server builded ower my own protocol > (small commands - max 50 bytes per command). But some time (aprox 10% from > total commands sent from server to client) we lost the data. And I can't > understand why and can't understand the relationship of what is happening. > Some time it's happens right after connections to client, some time after a > couple minutes after connect. Some time all ok. No any disconnects or error. > So my questions: > - how to be 100% sure that all data is delivered to client (by NodeJS > side)? > - if previous is impossible, how to check that my command is delivered? > > How to understand and when to use: > > - socket.setTimeout(timeout, > [callback])<http://nodejs.org/api/net.html#net_socket_settimeout_timeout_callback> > - > socket.setNoDelay([noDelay])<http://nodejs.org/api/net.html#net_socket_setnodelay_nodelay> > - socket.setKeepAlive([enable], > [initialDelay])<http://nodejs.org/api/net.html#net_socket_setkeepalive_enable_initialdelay> > > > Could these methods help me? > > P.s. It's our dev server with couple of clients. The network is stable, > ping 100%. > Sorry for my English. >
-- 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
