Yes. WebSocket++ only uses Boost features as polyfills for C++11 LANGUAGE features and libraries. If you have a C++11 compiler and standard library you can use WebSocket++ without Boost. In most cases setting your build environment to use the C++11 (or later) language dialect is sufficient to enable this mode of use.

With less common compilers (and sometimes very recently release compilers) there may be specific issues with CERTAIN libraries that aren't automatically detected by the library. For these situations there are ADDITIONAL defines available to fine tune which C++11 libraries and features are used. TODO: more details about them.

For the iostream/raw TRANSPORT the C++11 standard library is sufficient. For the Asio based transports, there is no C++11 library that provides the networking capabilities that Asio does. As such even with a C++11 build system, you will need a standalone copy of Asio to use if Boost Asio is not available.

Yes. WebSocket++ only uses Boost features as polyfills for C++11 language features and libraries. If you have a C++11 compiler and standard library you can use WebSocket++ without Boost. In most cases setting your build environment to use the C++11 (or later) language dialect is sufficient to enable this mode of use.

With less common compilers (and sometimes very recently release compilers) there may be specific issues with certain libraries that aren't automatically detected by the library. For these situations there are additional defines available to fine tune which C++11 libraries and features are used. TODO: more details about them.

For the iostream/raw transport the C++11 standard library is sufficient. For the Asio based transports, there is no C++11 library that provides the networking capabilities that Asio does. As such even with a C++11 build system, you will need a standalone copy of Asio to use if Boost Asio is not available.