3 ms·
Damn I just yesterday was pulling my hair out to get boost::beast to run (how unergonomic can an api be?!). Now I‘m considering to switch but what I really need
by WanderPanda 3y ago
Damn I just yesterday was pulling my hair out to get boost::beast to run (how unergonomic can an api be?!). Now I‘m considering to switch but what I really need is long term stability. I‘d rather like to not ever touch this code again, but it should compile over the next 5-10 years. I‘m not sure which one would be preferable in that regard
- jononor 3y agolibcurl? Old project, actively maintained, used in lots of embedded devices, maintainer understands the needs for stability, no silly rewrites.
- WanderPanda 3y agoAfaik libcurl is for clients only, but I also need to implement a server. Otherwise it sounds like exactly what I wish for from the governance perspective
- gary_0 3y agoThis looks promising: https://gitlab.com/eidheim/Simple-WebSocket-Server https://gitlab.com/eidheim/Simple-WebSocket-Server It includes http/https/ws/wss client and server code in just a few files (although last I checked, some files are needlessly duplicated in 2 different repos).
- fsloth 3y agolibcurl is excellent.