Differences between TCP sockets and web sockets, one more time [duplicate]

by

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 blocking socket or blocking send, then the number returned will match the size of the buffer but the call may block. With WebSockets, the data that is passed to the send method is always either sent as a whole “message” or not at all. Also, browser WebSocket implementations do not block on the send call.

But there are more important differences on the receiving side of things. When the receiver does a recv (or read) on a TCP socket, there is no guarantee that the number of bytes returned corresponds to a single send (or write) on the sender side. It might be the same, it may be less (or zero) and it might even be more (in which case bytes from multiple send/writes are received). With WebSockets, the recipient of a message is event-driven (you generally register a message handler routine), and the data in the event is always the entire message that the other side sent.

Note that you can do message based communication using TCP sockets, but you need some extra layer/encapsulation that is adding framing/message boundary data to the messages so that the original messages can be re-assembled from the pieces. In fact, WebSockets is built on normal TCP sockets and uses frame headers that contains the size of each frame and indicate which frames are part of a message. The WebSocket API re-assembles the TCP chunks of data into frames which are assembled into messages before invoking the message event handler once per message.

More Related Contents:

  1. What does “connection reset by peer” mean?
  2. Can two applications listen to the same port?
  3. When is TCP option SO_LINGER (0) required?
  4. What do you use when you need reliable UDP?
  5. TCP: can two different sockets share a port?
  6. Difference between socket and websocket?
  7. Do I need to heartbeat to keep a TCP connection open?
  8. Can TCP and UDP sockets use the same port?
  9. Go, tcp too many open files debug
  10. What’s the difference between WebSocket and plain socket communication?
  11. Does a TCP socket connection have a “keep alive”?
  12. What is the difference between 127.0.0.1 and localhost
  13. How to detect a remote side socket close? [duplicate]
  14. What are the use cases of SO_REUSEADDR?
  15. How to properly close socket in both client and server (python)
  16. Closing WebSocket correctly (HTML5, Javascript)
  17. Python Socket Multiple Clients
  18. Handling partial return from recv() TCP in C
  19. socket.emit() vs. socket.send()
  20. Writing to a closed, local TCP socket not failing
  21. Blocking sockets: when, exactly, does “send()” return?
  22. WebSockets ping/pong, why not TCP keepalive?
  23. Communicating with a socket.io server via c#
  24. ‘ab’ program freezes after lots of requests, why?
  25. Java TCP socket: data transfer is slow
  26. How can a WCF service listen the same port as IIS?
  27. Spurious readiness notification for Select System call
  28. Get Length of Data Available in NetworkStream
  29. TCP server with multiple Clients
  30. Run a web socket on Cloud Functions for Firebase?

Leave a Comment