tcpserver - node.js net module pings and messages not happening -

-

I have two nodes. Js applications that are running together on my server and I do not want to send server-side messages to them native node.js (v0.10.33) module using light net weight

I I intend the first app to send the second message. I'm listening to the console log ... ,

In the first app: 

  var push = ''; Var Net = Requirement ('Net'); Var server = net.createServer (function (p) {p.on ('error', function (err) {console.log (err);}); push = p; setInterval (function () {push.write (JSON ) .stringify ({'f': 'ping', 'data': 'survive'}));}, 1000);}); Server.listen (8008, function () {console.log ('listen ...')}); // A real message can be sent later in the application (this example would require a settime) push.written (JSON.stringify ({'f': 'msg', 'data': 'Hello World'}) );

In other applications I see the console log open 

  var net = required ('net'); Var pull = new net Socket (); Bridge.connect (8008, '127.0.0.1', function () {drag.log ('open'); drag ('data', function (_) {_ = JSON.parse (_); if (_ F === 'ping') {console.log ('!!! ping !!!');} else {console.log (.data);}}); pull.on ('error', function ( Error) {console.log ('bridge:' + error);});});

However I do not see any other activity (no ping, and later after the Open Event, Hello World) and no error.

If I do not see an event to accept data: ondata or onmessage

What is wrong? Unfortunately, I should tell that this messaging scheme is basically broken. You are using TCP.

Despite the fact that TCP sends its data to the IP packet, TCP is a packet protocol not a TCP socket is just an stream of data is thus wrong to see the data event as a logical message . In other words, at a one end, a socket. Written is not the same as a single data event on a single data in the event Multiple messages can be just one part of a message or message.

The good news is that a problem has already been solved many times. I either recommend:

  • This means for passing the JSON message on TCP.
  • Using some kind of pub-all messaging solution (this option makes your app more easy to scale)
  • If you know that your two apps are always If you run on the same machine, you should use the node.

Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more