OpenTelemetry instrumentation for `node:net` network API module
Turn a function into an `http.Agent` instance
The `@minecraft/server-net` module contains types for executing HTTP-based requests. This module can only be used on Bedrock Dedicated Server.
A Pulumi package for interacting with Docker in Pulumi programs
A tiny Node.js module to make any server force-closeable
Web3 module to interact with the Ethereum nodes networking properties.
The Swagger API toolchain for .NET, Web API and TypeScript.
A Pulumi package for creating and managing Cloudflare cloud resources.
A Pulumi package to create TLS resources in Pulumi programs.
A high-performance JavaScript 2D/3D polyline simplification library
A Pulumi package for creating and managing Datadog resources.
A node module for Google's Universal Analytics tracking
.Net dictionary for cspell.
An Error subclass that will chain nested Errors and dump nested stacktraces
A Pulumi package for creating and managing pagerduty cloud resources.
broccoli filter but with a persistent cache
A Pulumi package for creating and managing postgresql cloud resources.
A fully persistent balanced binary search tree
Edge.js: run .NET and Node.js in-process on Windows, Mac OS, and Linux
Observe when something in your node app starts listening on a TCP port
React Native TCP socket API for Android & iOS with SSL/TLS support
Parse and lookup IP network blocks
Support for OAuth 2(.1) and OpenId Connect (OIDC) in Angular
A Pulumi package for creating and managing auth0 cloud resources.
Manages persistent connections using Net::HTTP including a thread pool for connecting to multiple hosts. Using persistent HTTP connections can dramatically increase the speed of HTTP. Creating a new HTTP connection for every request involves an extra TCP round-trip and causes TCP congestion avoidance negotiation to start over. Net::HTTP supports persistent connections with some API methods but does not make setting up a single persistent connection or managing multiple connections easy. Net::HTTP::Persistent wraps Net::HTTP and allows you to focus on how to make HTTP requests.
Faraday adapter for NetHttpPersistent
Manages persistent connections using Net::HTTP. It's thread-safe too! Using persistent HTTP connections can dramatically increase the speed of HTTP. Creating a new HTTP connection for every request involves an extra TCP round-trip and causes TCP congestion avoidance negotiation to start over. Net::HTTP supports persistent connections with some API methods but does not handle reconnection gracefully. Net::HTTP::Persistent supports reconnection and retry according to RFC 2616.
Manages persistent connections using Net::HTTP plus a speed fix for Ruby 1.8. It's thread-safe too! Using persistent HTTP connections can dramatically increase the speed of HTTP. Creating a new HTTP connection for every request involves an extra TCP round-trip and causes TCP congestion avoidance negotiation to start over. Net::HTTP supports persistent connections with some API methods but does not handle reconnection gracefully. Net::HTTP::Persistent supports reconnection and retry according to RFC 2616.
This is an experimental branch that implements a connection pool of Net::HTTP objects instead of a connection/thread. C/T is fine if you're only using your http threads to make connections but if you use them in child threads then I suspect you will have a thread memory leak. Also, I want to see if I get less connection resets if the most recently used connection is always returned. Also added a :force_retry option that if set to true will retry POST requests as well as idempotent requests. This branch is currently incompatible with the master branch in the following ways: * It doesn't allow you to recreate the Net::HTTP::Persistent object on the fly. This is possible in the master version since all the data is kept in thread local storage. For this version, you should probably create a class instance of the object and use that in your instance methods. * It uses a hash in the initialize method. This was easier for me as I use a HashWithIndifferentAccess created from a YAML file to define my options. This should probably be modified to check the arguments to achieve backwards compatibility. * The method shutdown is unimplemented as I wasn't sure how I should implement it and I don't need it as I do a graceful shutdown from nginx to finish up my connections. For connection issues, I completely recreate a new Net::HTTP instance. I was running into an issue which I suspect is a JRuby bug where an SSL connection that times out would leave the ssl context in a frozen state which would then make that connection unusable so each time that thread handled a connection a 500 error with the exception "TypeError: can't modify frozen". I think Joseph West's fork resolves this issue but I'm paranoid so I recreate the object. Compatibility with the master version could probably be achieved by creating a Strategy wrapper class for GenePool and a separate strategy class with the connection/thread implementation.
Manages persistent connections using Net::HTTP plus a speed fix for Ruby 1.8. It's thread-safe too! Using persistent HTTP connections can dramatically increase the speed of HTTP. Creating a new HTTP connection for every request involves an extra TCP round-trip and causes TCP congestion avoidance negotiation to start over. Net::HTTP supports persistent connections with some API methods but does not handle reconnection gracefully. Net::HTTP::Persistent supports reconnection and retry according to RFC 2616.
Hugs net-http-persistent with convenient get, delete, post, and put methods.
A persistent Net::Http adapter for Faraday with a connection pool shared across threads and fibres.
A micro single room Campfire interface that only depends on Net::HTTP::Persistent and a JSON library. On 1.9, it will use Psych by default, on other rubies it will try for yajl, then for json.
Safe defaults, persistent connections, thread safety, and basic logging for Ruby's Net::HTTP library
This is an update to the old `gem mirror` command. It uses net/http/persistent and threads to grab the mirror set a little faster than the original. Eventually it will replace `gem mirror` completely. Right now the API is not completely stable (it will change several times before release), however, I will maintain stability in master.
No description provided.
No description provided.