This question is similar to asking the difference between TCP and HTTP. I shall still try to address your question, its natural to get confused between these two terms if you are beginning. Short Answer STOMP is derived on top of WebSockets. STOMP just mentions a few specific ways on how the message frames are … Read more
Some notes. koush/AndroidAsync does not perform the closing handshake which is required by RFC 6455. See this for details. Project Tyrus works on Android, but make sure that its license (CDDL 1.1 and GPL 2 with CPE) and its size (Reducing WebSocket client jar size with ProGuard) meet your requirements. Also note that Tyrus may … Read more
Here is what I ended up with. It works for my purposes. function connect() { var ws = new WebSocket(‘ws://localhost:8080’); ws.onopen = function() { // subscribe to some channels ws.send(JSON.stringify({ //…. some message the I must send when I connect …. })); }; ws.onmessage = function(e) { console.log(‘Message:’, e.data); }; ws.onclose = function(e) { console.log(‘Socket … Read more
There is no Javascript API to send ping frames or receive pong frames. This is either supported by your browser, or not. There is also no API to enable, configure or detect whether the browser supports and is using ping/pong frames. There was discussion about creating a Javascript ping/pong API for this. There is a … 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
In most ways WebSockets will probably scale better than AJAX/HTML requests. However, that doesn’t mean WebSockets is a replacement for all uses of AJAX/HTML. Each TCP connection in itself consumes very little in terms server resources. Often setting up the connection can be expensive but maintaining an idle connection it is almost free. The first … Read more
This article may help you along the way: http://drewww.github.io/socket.io-benchmarking/ I wondered the same question, so I ended up writing a small test (using XHR-polling) to see when the connections started to fail (or fall behind). I found (in my case) that the sockets started acting up at around 1400-1800 concurrent connections. This is a short … Read more
Use a secure URL for your initial connection, i.e. instead of “http://” use “https://”. If the WebSocket transport is chosen, then Socket.IO should automatically use “wss://” (SSL) for the WebSocket connection too. Update: You can also try creating the connection using the ‘secure’ option: var socket = io.connect(‘https://localhost’, {secure: true});
When you send bytes from a buffer with a normal TCP socket, the send function returns the number of bytes of the buffer that were sent. If it is a non-blocking socket or a non-blocking send then the number of bytes sent may be less than the size of the buffer. If it is a … Read more
It’s easier to communicate via TCP sockets when you’re working within an intranet boundary, since you likely have control over the machines on that network and can open ports suitable for making the TCP connections. Over the internet, you’re communicating with someone else’s server on the other end. They are extremely unlikely to have any … Read more