Open Source HTTP Clients

The C++ REST SDK is a Microsoft project for cloud-based client-server communication in native code using a modern asynchronous C++ API design. This project aims to help C++ developers connect to and interact with services. cpprestsdk is in maintenance mode and we do not recommend its use in new projects. We will continue to fix critical bugs and address security issues. Once you have the library, look at our tutorial to use the http_client. It walks through how to setup a project to use the C++ Rest SDK and make a basic Http request. HTTP client/server, JSON, URI, asynchronous streams, WebSockets client, oAuth. A powerful model for composing asynchronous operations based on C++ 11 features. Windows desktop, Windows Store (UWP), Linux, OS X, Unix, iOS, and Android. Support for Visual Studio 2015 and 2017 with debugger visualizers.

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

!!! 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...

Flea2Flea is a pocket web server written in Java which enables ad-hoc peer-to-peer file sharing with anyone who has an http client (web browser). Files are only accessible while you are running Flea2Flea. You have absolute control.

Client/server network communication library using non-blocking I/O. Also a simple HTTP client/server.

Infinitely transfer between every device over pure HTTP with pipes or browsers. Piping Server transfers data to POST /hello or PUT /hello into GET /hello. The path /hello can be anything such as /mypath or /mypath/123/. A sender and receivers who specify the same path can transfer. Both the sender and the recipient can start the transfer first. The first one waits for the other. The most important thing is that the data are streamed. This means that you can transfer any data infinitely. The demo below transfers an infinite text stream with seq inf. You can transfer any kind of data infinitely on a stream. Streams are very efficient in terms of both time and space. All you need is to have either a Web browser or curl, which are widely pre-installed. You do not need to install any extra software.

The client sends a friend text message (supports websocket and HTTP). The client obtains the wxid and name of the friend in the address book (supports websocket and HTTP). The client sends a picture to a friend (supports websocket and HTTP). Sends an AT message (support websocket and HTTP). Send attachments (only support HTTP, weboscket). Get chatroom member list (wxid) and nickname (support websocket and HTTP). Please refer to the sample code of client.js (websocket client) and httpclient.js (http client). You can inject it once. If you want to re-inject, please exit WeChat, restart WeChat and then inject it.