It looks like IE throws a SecurityError if you’re trying to open a websocket on a local (intranet) domain. To overcome this, you may disable IE’s automatic algorithm for recognizing local sites. This can be done in Tools > Internet Options > Security > Local Intranet > Sites. Uncheck all checkboxes (or only a particular … Read more
Even though @MessageMapping supports placeholders, they are not exposed / resolved in @SendTo destinations. Currently, there’s no way to define dynamic destinations with the @SendTo annotation (see issue SPR-12170). You could use the SimpMessagingTemplate for the time being (that’s how it works internally anyway). Here’s how you would do it: @MessageMapping(“/fleet/{fleetId}/driver/{driverId}”) public void simple(@DestinationVariable String … Read more
Yes, the answer is still ‘no’. Websockets are TCP based. Note that a WebSocket is not a plain TCP connection, there is HTTP negotiation and a framing protocol in place. So you also cannot create a plain TCP connection in Javascript. WebRTC is based on UDP, it may cover your use cases: http://www.html5rocks.com/en/tutorials/webrtc/datachannels/
Try Chrome’s developer tools, click ‘Network’ tab use the filters at the bottom to show only WebSocket connections), select the desired websocket connection, note that there are ‘Headers’, ‘Preview’, ‘Response’, etc. sub-tabs to the right, once data starts flowing a ‘WebSocket Frames’ subtab will appear. All data going in either direction is logged. Very informative.
Others have hinted at this in other answers and comments, but the root problem is that Socket.IO is just a delivery mechanism, and you cannot depend on it alone for reliable delivery. The only person who knows for sure that a message has been successfully delivered to the client is the client itself. For this … Read more
Not to say that the other answers here don’t have merit, they make some good points. But I’m going to go against the general consensus and agree with you that moving to websockets for more than just realtime features is very appealing. I am seriously considering moving my app from a RESTful architecture to more … Read more
On today’s systems, handling 1 million concurrent TCP connections is not an issue. I can affirm that based on our own tests (full disclosure: I am the CTO at Lightstreamer). We had to demonstrate several times, to some of our customers, that 1 million connections can be reached on a single box (and not necessarily … Read more
Here’s a summary of the tradeoffs I’m aware of. Reasons to use webSocket: You need/want server-push of data. You are sending lots of small pieces of data from client to server and doing it very regularly. Using webSocket has significantly less overhead per transmission. Reasons to use REST: You want to use server-side frameworks or … Read more
Chrome itself is emitting these messages, and there is no way to block them. This is a function of how chrome was built; whenever a ResourceFetcher object attempts to fetch a resource, its response is passed back to its context, and if there’s an error, the browser prints it to the console – see here. … Read more
Javascript supports WebSocket, so you don’t need an additional client side framework to use it. Please take a look at this $connection service declared in this WebSocket based AngularJS application. Basically you can listen for messages: $connection.listen(function (msg) { return msg.type == “CreatedTerminalEvent”; }, function (msg) { addTerminal(msg); $scope.$$phase || $scope.$apply(); }); Listen once (great … Read more