Open Source C HTTP Clients

The AWS IoT Device SDK for Embedded C (C-SDK) is a collection of C source files under the MIT open source license that can be used in embedded applications to securely connect IoT devices to AWS IoT Core. It contains MQTT client, HTTP client, JSON Parser, AWS IoT Device Shadow, AWS IoT Jobs, and AWS IoT Device Defender libraries. This SDK is distributed in source form and can be built into customer firmware along with application code, other libraries, and an operating system (OS) of your choice. These libraries are only dependent on standard C libraries, so they can be ported to various OS's - from embedded Real-Time Operating Systems (RTOS) to Linux/Mac/Windows. You can find sample usage of C-SDK libraries on POSIX systems using OpenSSL (e.g. Linux demos in this repository), and on FreeRTOS using mbedTLS (e.g. FreeRTOS demos in the FreeRTOS repository). The coreHTTP library provides the ability to establish an HTTP connection with a server over a customer-implemented transport layer.

Like libevent, libev, and libuv, libhv provides event loop with non-blocking IO and timer, but simpler api and richer protocols. Cross-platform (Linux, Windows, MacOS, BSD, Solaris, Android, iOS) High-performance EventLoop (IO, timer, idle, custom) TCP/UDP client/server/proxy. TCP supports heartbeat, reconnect, upstream, MultiThread-safe write and close, etc. Built-in common unpacking modes (FixedLength, Delimiter, LengthField) RUDP support: WITH_KCP. SSL/TLS support: (via WITH_OPENSSL or WITH_GNUTLS or WITH_MBEDTLS) HTTP client/server (support https http1/x http2 grpc). HTTP supports static service, indexof service, proxy service, sync/async API handler. HTTP supports RESTful, router, middleware, keep-alive, chunked, SSE, etc. WebSocket client/server.

Puf is a command line web (HTTP) client. It is similar to GNU wget (and has similar options), but has the ability to do many downloads in parallel. Of course, it supports recursive fetching.

!!! I don't have a SVN client anymore, I moved my code to CodeBerg, in Europe (and so should you): https://codeberg.org/tygre !!! IF YOU LIKE IT, BUY ME A COFFEE AT https://www.buymeacoffee.com/amimodradio MORE INFORMATION AT http://www.chingu.asia/wiki/index.php?title=AmiModRadio Did you know that, as of today (2015/06/02), there are more than 20,000 packages (http://aminet.net/tree) in the mods directory on Aminet? Yes! That's more than 20,000 modules to play and enjoy! So, why not have a program that could automatically download one module at-a-time, extract it, and play it? This is the purpose of AmiModRadio...

Highly portable API written in C that implements the client side of the HTTP 1.1 Protocol as Defined in RFC 2616,2617. Can be easily ported to any platform that supports standard C calls and Berkeley sockets.

The OwnTracks Recorder is a lightweight program for storing and accessing location data published via MQTT (or HTTP) by the OwnTracks apps. It is a compiled program which is easy to install and operate even on low-end hardware, and it doesn't require an external database. There are two main components: the Recorder obtains data via MQTT subscribes or HTTP POST, stores the data in plain files and serve it via its built-in REST API, and the ocat command-line utility reads stored data in a variety of formats. We developed the Recorder as a one-stop solution to storing location data published by our OwnTracks apps (iOS and Android) and retrieving this data. Our previous offerings (m2s, o2s/Pista) also work of course, but we believe the Recorder is best suited to most environments.

Most modern networking is built either on slow and ambiguous REST APIs or unnecessarily complex gRPC. FastAPI, for example, looks very approachable. We aim to be equally or even simpler to use. It takes over a millisecond to handle a trivial FastAPI call on a recent 8-core CPU. In that time, light could have traveled 300 km through optics to the neighboring city or country, in my case. How does UCall compare to FastAPI and gRPC? How can a tiny pet-project with just a couple thousand lines of code compete with two of the most established networking libraries? UCall stands on the shoulders of Giants.

A combination of the rsync algorithm and content-addressable storage. An efficient way to store and retrieve multiple related versions of large file systems or directory trees. An efficient way to deliver and update OS, VM, IoT and container images over the Internet in an HTTP and CDN friendly way. Let's take a large linear data stream, split it into variable-sized chunks (the size of each being a function of the chunk's contents), and store these chunks in individual, compressed files in some directory, each file named after a strong hash value of its contents, so that the hash value may be used to as key for retrieving the full chunk data. Let's call this directory a "chunk store". At the same time, generate a "chunk index" file that lists these chunk hash values plus their respective chunk sizes in a simple linear array. The chunking algorithm is supposed to create variable, but similarly sized chunks from the data stream.

Advanced C/C++ library(ACL) for UNIX-like OS and WIN32 OS, including sync/async/ssl iostream for net/file, thread pool, process pool, db pool, server framework, event, memory, string, array/hash/ring/list, xml and json parser, http/smtp/icmp protocol, SSL/TLS, C unit test, etc