libunifex
beast
libunifex | beast | |
---|---|---|
22 | 5 | |
1,366 | 53 | |
2.5% | - | |
7.6 | 0.0 | |
10 days ago | over 1 year ago | |
C++ | C++ | |
GNU General Public License v3.0 or later | Boost Software License 1.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
libunifex
-
Comparing asio to unifex
I'm curious what led you to this conclusion. If you ran into scalability issues with its static_thread_pool, then that's a known issue. If it's something else, the authors (of which I'm one) would love to know.
-
How does one actually build a C++ project
Instead of calling add_executable you will call add_library. Here is a (only moderately complicated) production example of a library that can be built standalone (along with tests and example executables), or as a subproject, where it builds only the library
-
How to write networking code now that will be easiest to adapt to the upcoming standard?
My original thought was to build my DDS implementation on top of libunifex in anticipation for standardization: https://github.com/facebookexperimental/libunifex
-
Executors/libunifex example project
I'm trying to understand how to work with the proposed executors in a project, but after watching Eric Niebler's cppcon talks (https://youtu.be/xLboNIf7BTg) and looking at the libunifex examples (https://github.com/facebookexperimental/libunifex/tree/main/examples) I still have a hard time wrapping my head around how to employ the sender/receiver pattern in a larger project.
-
Async/Await pattern in C++
You have coroutines in C++20 but there is also the executives proposal that's making it's way into C++23 that is available as a library under the name unifex that only requires C++14
-
Using Asio for asynchronous gRPC clients and servers
Asio-grpc makes exactly that possible by providing an Asio execution_context compatible interface to the CompletionQueue. It supports all types of RPCs (including generic ones), completion tokens, cancellation, as well as libunifex sender/receiver (if you want to try out what might become std::execution). The latest release (v1.7.0) also introduced a GrpcStream class for writing Rust/Golang select-style code.
-
My thoughts and dreams about a standard user-space I/O scheduler
P2300: they are trying to standardize facebookexperimental/libunifex
-
"C++ makes it harder to shoot yourself, but when you do it blows your whole leg off"
All the network handling for Instagram and all other Meta apps on all platforms is handled by their own C++ library https://github.com/facebookexperimental/libunifex.
-
State of the art for CPOs (customization points) in C++?
This. I'd also like to mention libunifex. It's entirely based on tag_invoke and is a testament as to how much power it actually provides. On the other hand, it also proves how cumbersome it is to define CPOs with tag_invoke. But IMO it's a lot better than anything else anyone has ever created, and users usually don't need to define new CPOs, only library writers do, so there's that.
-
Why do we need networking, executors, linear algebra, etc in the Standard Library?
A work in progress implementation of the library: https://github.com/facebookexperimental/libunifex
beast
-
Download from Google drive
It appears that Google wrote some utilities to do this without manually having to deal with HTTP, but they are only available in Java, Python, Node.js, PHP and .NET - not C++. So you will have to write your own C++ library that sends HTTP requests to the web API and handles the received messages and data. You will need some library to handle network sockets and HTTP requests, such as libcurl or Boost Beast (or see under Communication here: https://en.cppreference.com/w/cpp/links/libs)
- How to build Web servers using C++ (Fun project for Beginners)
-
My thoughts and dreams about a standard user-space I/O scheduler
For example Boost-Beast and Boost-Mysql(not officially boost) receive user provided asio::io_context and every other library in this ecosystem should be the same.
-
Creating a GUI that can interact with web API.
Otherwise, Boost has an HTTP library: https://github.com/boostorg/beast
-
How and where I can learn about Web sockets, APIs, Wrappers to connect with my C++ code?
Docs, GitHub
What are some alternatives?
cppcoro - A library of C++ coroutine abstractions for the coroutines TS
rsocket-cpp - C++ implementation of RSocket
concurrencpp - Modern concurrency for C++. Tasks, executors, timers and C++20 coroutines to rule them all
RapidJSON - A fast JSON parser/generator for C++ with both SAX/DOM style API
Taskflow - A General-purpose Parallel and Heterogeneous Task Programming System
Restbed - Corvusoft's Restbed framework brings asynchronous RESTful functionality to C++14 applications.
POCO - The POCO C++ Libraries are powerful cross-platform C++ libraries for building network- and internet-based applications that run on desktop, server, mobile, IoT, and embedded systems.
corrade - C++11 multiplatform utility library
Boost.Beast - HTTP and WebSocket built on Boost.Asio in C++11
Folly - An open-source C++ library developed and used at Facebook.
llfio - P1031 low level file i/o and filesystem library for the C++ standard