Search Results for "ssl library"

Ultra-fast and low latency asynchronous socket server & client C++ library with support TCP, SSL, UDP, HTTP, HTTPS, WebSocket protocols, and 10K connections problem solution. Cross platform (Linux, MacOS, Windows) Asynchronous communication. Supported CPU scalability designs: IO service per thread, thread pool. Supported transport protocols: TCP, SSL, UDP, UDP multicast. Supported Web protocols: HTTP, HTTPS, WebSocket, WebSocket secure.

urllib3 is a powerful, user-friendly HTTP client for Python. Much of the Python ecosystem already uses urllib3 and you should too. Thread safety, connection pooling. Client-side TLS/SSL verification. File uploads with multipart encoding. Helpers for retrying requests and dealing with HTTP redirects. Support for gzip, deflate, brotli, and zstd encoding. Proxy support for HTTP and SOCKS. 100% test coverage. Professional support for urllib3 is available as part of the Tidelift Subscription....

Requests is a HTTP library written in PHP, for human beings. It is roughly based on the API from the excellent Requests Python library. Requests is ISC Licensed (similar to the new BSD license) and has no dependencies, except for PHP 5.6+. Despite PHP’s use as a language for the web, its tools for sending HTTP requests are severely lacking. cURL has an interesting API, to say the least, and you can’t always rely on it being available. Sockets provide only low-level access and require you to...

Ultra fast and low latency asynchronous socket server & client C# .NET Core library with support TCP, SSL, UDP, Unix Domain Socket, HTTP, HTTPS, WebSocket protocols and 10K connections problem solution. Has an integration with high-level message protocol based on Fast Binary Encoding. Cross-platform (Linux, MacOS, Windows) Asynchronous communication. Supported transport protocols: TCP, SSL, UDP, UDP multicast, Unix Domain Socket.

Header Only Cross-platform high-performance TCP network library using C++ 11. The server uses two network threads and one logic thread, the client uses one network (also process logic) thread. Every packet size is 46 bytes. Every packet contains the client's id. Server broadcast packets to all clients when recv one packet from any client. The client sends one packet when recv packet from the server and the packet's id is equal self.