Search Results for "sockets"

...Executing external program and making it communicate to WebSocket using stdin/stdout. Text and binary modes, converting between lines (or null-terminated records) and messages. Inetd mode, UNIX sockets (including abstract namespaced on Linux). Integration with Nginx using TCP or UNIX sockets. Directly using unauthenticated SOCKS5 servers for connecting to WebSockets and listening WebSocket connections. Auto-reconnect and connection-reuse modes. Linux, Windows, and Mac support, with pre-built executables. Low-level WebSocket clients and servers with an overridable underlying transport connection, e.g. calling an external program to serve as a transport for websocat (for SSL, proxying, etc.).

...At a high level, Tokio provides a number of components needed for building asynchronous applications. These include a multithreaded, work-stealing based task scheduler; a reactor that's supported by the operating system's event queue; and asynchronous TCP and UDP sockets. Tokio is reliable in that its APIs are memory-safe, thread-safe, and misuse-resistant. Thanks to its task scheduler, it is also incredibly fast. It is capable of processing hundreds of thousands of requests per second with little to no overhead.

...It uses Results for reporting errors, bitflags instead of bare integer flags, an Arg trait with optimizations to efficiently accept any Rust string type, and several other efficient conveniences. rustix is low-level and, and while the net API supports Windows Sockets 2 (Winsock), the rest of the APIs do not support Windows; for higher-level and more portable APIs built on this functionality, see the cap-std, memfd, timerfd, and io-streams crates.

hyper is a fast HTTP implementation written in and for Rust. A Client for talking to web services. A Server for building those web services. Blazing fast thanks to Rust. High concurrency with non-blocking sockets. HTTP/1 and HTTP/2 support. hyper is a relatively low-level library, meant to be a building block for libraries and applications. If you are looking for a convenient HTTP client, then you may wish to consider reqwest. If you are looking for a convenient HTTP server, then you may wish to consider warp. Both are built on top of this library. ...

Open source HTTP reverse proxy built in Rust for immutable infrastructures. Most existing tools have a static vision of production: a service is installed once on a long-lived server, updated from time to time, with configuration rarely changing. There's now a shift in infrastructure to short-lived virtual machines and hundreds of new deployments per day, and the usual tools reach their limits. How do we reconcile a dynamic environment with availability guarantees? How can we get "zero...

...Because tasks do not need to be Send or Sync and can make use of thread-local data safely, Monoio simplifies certain concurrency paradigms while delivering performance benefits for workloads like high-throughput network servers, proxies, or real-time services. The runtime includes abstractions for async sockets, readers/writers, TCP/UDP networking, and compatibility layers (macros, crates) to ease adoption.

...OpenEthereum is licensed under the GPLv3 and can be used for all your Ethereum needs. By default, OpenEthereum runs a JSON-RPC HTTP server on port :8545 and a Web-Sockets server on port :8546. This is fully configurable and supports a number of APIs. You can generate documentation for OpenEthereum Rust packages that automatically opens in your web browser.

...Parity Ethereum is licensed under the GPLv3 and can be used for all your Ethereum needs. By default, Parity Ethereum runs a JSON-RPC HTTP server on port :8545 and a Web-Sockets server on port :8546. This is fully configurable and supports a number of APIs. If you run into problems while using Parity Ethereum, check out the wiki for documentation, feel free to file an issue in this repository, or hop on our Gitter or Riot chat room to ask a question. We are glad to help!