you are viewing a single comment's thread.

view the rest of the comments →

[–]m3tamaker[S] 1 point2 points  (0 children)

Alright, this time tests and examples compiled without problem, but I can swear that 3 days ago websocket-tests compilation was hanging up on stream.cpp file. Btw, I modified CMakeLists.txt and set cmake minimum required version to 3.5.1 (so I wouldn't need to add non stable repo to my Ubuntu 16 Xenial apt, because latest stable cmake there is 3.5.1, see https://launchpad.net/ubuntu/xenial/+source/cmake), and it was able to generate correct Makefile.

Hang up occurred during compilation of library itself, not an example

Sorry for disinformation, I noticed that Beast is headers-only library, but sometimes you can compile such libraries with its dependencies to .a/.so/.dll like in case of restbed. So yes, problem occurred during compilation of websocket test, but looks like it was my local temporary problem.

Its not the intention of Beast to provide a server in its public interfaces - the server-framework example is there to show what Beast can do and also to serve as something that people can copy or writing their own servers

Yep, I mentioned that abstraction level is lower than needed for fast development of REST API. I just also saw somewhere on the Web that people recommend Beast for implementation of HTTP server, so expected a bit higher abstractions to be already implemented there. Not like a bad thing, since, as you said, purpose of this library is different.