libquic alternatives and similar libraries
Based on the "Networking" category.
Alternatively, view libquic alternatives based on common mentions on social networks and blogs.
-
uWebSockets
µWS is one of the most lightweight, efficient & scalable WebSocket & HTTP server implementations available. [Zlib] -
POCO
C++ class libraries and frameworks for building network- and internet-based applications that run on desktop, server, mobile and embedded systems. [Boost] website -
libwebsockets
Libwebsockets is a lightweight pure C library built to use minimal CPU and memory resources, and provide fast throughput in both directions as client or server -
cpr
A modern C++ HTTP requests library with a simple but powerful interface. Modeled after the Python Requests module. [MIT] website -
Simple-Web-Server
A very simple, fast, multithreaded, platform independent HTTP and HTTPS server and client library implemented using C++11 and Boost.Asio. Created to be an easy way to make REST resources available from C++ applications. -
wdt
An embeddedable library (and command line tool) aiming to transfer data between 2 systems as fast as possible over multiple TCP paths. [BSD-3-Clause] -
Simple-WebSocket-Server
A very simple, fast, multithreaded, platform independent WebSocket (WS) and WebSocket Secure (WSS) server and client library implemented using C++11, Boost.Asio and OpenSSL. Created to be an easy way to make WebSocket endpoints in C++. -
nope.c
A C language-based ultra-light software platform for scalable server-side and networking applications. Think node.js for C programmers. [GPL2] -
NetIF
Header-only C++14 library for getting network addresses associated with network interface without name lookups on Windows, macOS, Linux, and FreeBSD
Get performance insights in less than 4 minutes
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of libquic or a related project?
Popular Comparisons
README
QUIC, a multiplexed stream transport over UDP
QUIC is an experimental protocol aimed at reducing web latency over that of TCP. On the surface, QUIC is very similar to TCP+TLS+SPDY implemented on UDP. Because TCP is implemented in operating system kernels, and middlebox firmware, making significant changes to TCP is next to impossible. However, since QUIC is built on top of UDP, it suffers from no such limitations.
Key features of QUIC over existing TCP+TLS+SPDY include
- Dramatically reduced connection establishment time
- Improved congestion control
- Multiplexing without head of line blocking
- Forward error correction
- Connection migration
See Chromium QUIC Page for detailed information.
libquic
This repository is sources and dependencies extracted from Chromium's QUIC Implementation with a few modifications and patches to minimize dependencies needed to build QUIC library.
Notable and only dependency is BoringSSL. The BoringSSL sources is already embedded in this repository and linked with CMake build file. You don't need any kind of dependency installs.
Language Bindings
This library is intended as an essential reference point for other language bindings and possibly for integration with other C/C++ codebase such as HTTP servers like Apache or nginx.
Currently there is only one experimental language binding:
- Go binding: goquic
Getting Started
How to build
Building with CMake and Ninja (Recommended):
$ mkdir build/
$ cd build/
$ cmake -GNinja ..
$ ninja
Building with CMake and Make:
$ mkdir build/
$ cd build/
$ cmake ..
$ make -j 4
make -j limits the number of simultaneously executed Recepies. Adapt this number to the capabilities of your build machine.
libquic.a
library file will be generated. libssl.a
, libcrypto.a
will be
located in build/boringssl directory.
To do release builds run $ cmake -GNinja -DCMAKE_BUILD_TYPE=Release ..
instead
of $ cmake -GNinja ..
.
How to integrate
In order to integrate libquic to your code, your best source of documentation is official Chromium QUIC toy client and server. Golang binding will help too.
Syncing from Upstream
Great effort has been made to make syncing from upstream Chromium sources as
effortless as possible. See DEPS
file for all the dependencies. See
manage.py
script for actual syncing.
If you want to apply upstream changes,
- Clone & Checkout chromium upstream.
- Build QUIC server:
cd out/Debug; ninja quic_server
- Update "chromium_revision" var at DEPS to your chromium source code revision.
- Do
./sync.py <CHROMIUM_GIT_ROOT>
All necessary files will be updated to new ones without patches applied. - Temporarily commit here.
- Do
./sync.py <CHROMIUM_GIT_ROOT>
--patch All the patches will be applied. Some patches will be rejected. - If there is any patch collision, manually apply the rejected patches.
Open the
*.rej
files and carefully apply the rejected hunks manually. - Try build, and you'll find that you may need to add additional
modifications to make build successful. There may be added or deleted
source files. Update
CMakeLists.txt
accordingly. - If the build is successful, make a patch by:
git diff src/ > patch/basepatch.patch
(Make sure you don't includecustom/
directory sources to the patch) - Add patch file to
DEPS
or update existing patch files. Amend previous commit. - Commit
DEPS
, new patch, and source changes