node.js - NodeJS (coffeescript): TCP socket only writing intermittently -


i having trouble setting simple simple server using net module in nodejs keeps each tcp socket open once connected, reads data socket , replies/writes data socket after each line of text received.

i receiving data lines/chunks/requests , each 1 write response string socket. however, of written responses being received client.

below simplified code server:

net = require('net')  server = net.createserver() nl = string.fromcharcode(10)  server.on('connection', (socket) ->   console.log('net server connection')    handle = (data, next) ->     if data.tostring().indexof('@command;') > -1       console.log("sending: #{"@none\n"}")       socket.write("@none#{nl}", next)     else       console.log("sending: mf;ok;9999-9999")       socket.write("mf;ok;9999-9999#{nl}", next)    socket.on('end', () ->     console.log('client disconnected')   )    socket.on('data', (data) ->     console.log("recieved: #{data}")     console.log("pausing")     socket.pause()     handle(data, () ->       socket.resume()       console.log("resuming")     )   )    socket.on('error', (err) ->     winston.error("socket error: ", err)   ) )  server.on('listening', () -> console.log('net server listening')) server.on('error', (err) -> console.log('net server error', err)) server.on('close', (err) -> console.log('net server close')) server.listen(8888)

the client not have control on has been tested working fine.

this desired output:

tx: @tr;mf;1234;3;1;1;999999;12345;# rx: mf;ok;9999-9999 tx: @tr;mf;1235;2;1;11111;22222;33333;44444;1;2;13579;30.23;1090.23;0;1;12345;# rx: mf;ok;9999-9999 tx: @command;12345 rx: @none

and actual output: (you'll notice line 4 missing).

tx: @tr;mf;1234;3;1;1;999999;12345;# rx: mf;ok;9999-9999  tx: @tr;mf;1235;2;1;11111;22222;33333;44444;1;2;13579;30.23;1090.23;0;1;12345;# tx: @command;12345 rx: @none

and here console.log output in terminal:

net server connection recieved: @tr;mf;1234;3;1;1;999999;12345;# pausing sending: mf;ok;9999-9999 resuming recieved: @tr;mf;1235;2;1;11111;22222;33333;44444;1;2;13579;30.23;1090.23;0;1;12345;# pausing sending: mf;ok;9999-9999 resuming recieved: @command;12345 pausing sending: @none

where going wrong!? in advance

there nothing wrong code. problem on client side. need need answers. thanks


Comments

Post a Comment

Popular posts from this blog

html - Outlook 2010 Anchor (url/address/link) -

i'm trying link specific pdf page msoutlook'10 or msword'10, #page=... anchor particularly useful , works fine elsewhere. unfortunately when click [ctr-k] in outlook or winword, links re-formatted assuming unc path. pdf file located on shared drive. using "file:" prefix links open pdf in adobe reader (outside of browser), , "http:" open inside browser. issue seem need open in browser "file:" prefix in order anchor work. know anchors work inside browser. outlook uses windows/explorer default program (based on file extension) seems open in adobe reader neglecting anchor. is aware of solution, link specific page or bookmark of shared-pdf ms outlook and/or winword link? common references: mailermailer.com/...anchor-tags-html-emails campaignmonitor.com/...anchor-links-in-email-newsletters/ stackoverflow.com/...anchor-in-pdf-document
Read more

javascript - Why does running this loop 9 times take 100x longer than running it 8 times? -

consider code: test = function() { } t = new test(); (var = 0; < 8; i++) { result = t instanceof test; } if change number of iterations 8 9 , loop take 100 times longer complete in latest version of firefox (41.0.1). tested on 2 different pcs , magic limit 8. here jsperf test used: http://jsperf.com/instanceof-8-times-vs-9-times does have idea why might happen? seems specific instanceof . not happen if else object, example check property. note: filed bugzilla bug this. jan de mooij mozilla team has posted details in bugzilla thread . here's simplistic interpretation of highly technical answers: in i < 8 case, firefox smart enough hoist result = t instanceof test; statement out of loop (according tests, doesn't seem omit altogether). in i < 9 case, apparently doesn't optimization . why? reason not clear, related fact 9 iterations threshold above function considered "hot" enough run through jit compiler. i < 8 cas...
Read more

Getting gateway time-out Rails app with Nginx + Puma running on Digital Ocean -

following this guide setup app on digital ocean droplet, not working. site not loading , it's throwing: "gateway time-out". the puma server works, since ps aux | grep puma prints: root 15878 0.0 0.4 376832 2168 ? sl 12:50 0:00 puma 2.13.4 (unix:///var/www/myapp/shared/tmp/sockets/myapp-puma.sock) [20150930164940] root 15881 0.0 0.7 903676 3692 ? sl 12:50 0:06 puma: cluster worker 0: 15878 [20150930164940] root 24654 0.0 0.1 11748 916 pts/2 s+ 18:00 0:00 grep --color=auto puma my nginx config: user root; worker_processes 1; events { worker_connections 1024; } http { upstream puma { server unix:///var/www/myapp/shared/tmp/sockets/myapp-puma.sock; } server { listen 80; server_name myapp.com; root /var/www/myapp/current/public; access_log /var/www/myapp/current/log/access.log; error_log /...
Read more