1. 12
  1.  

  2. 4

    I’ve kicked the tires of a lot of C/C++ WebSocket libraries over the past few years. Some quick notes on this one, after skimming the code:

    • I imagine this isn’t aimed at servers, because on a server who cares if the code is tiny? And thread-per-connection doesn’t scale well.
    • But on a client system, you’d really need built-in TLS support.
    • It looks like this is Linux-only, judging by the absence of any per-platform ifdefs. In my experience, dealing with different OSs is the most painful part of C/C++ network code.
    1. 2

      I imagine this isn’t aimed at servers, because on a server who cares if the code is tiny?

      Depends on your definition of Server. Is a Raspberry in your basement a server?

      Also the benefit of a tiny implementation is that it’s easy to understand and change for your needs.