> It's a toolkit for simplfing development, including several common-used Server Protocols(http1.1, https, http2).
NEO•ONE Server http client api.
NEO•ONE Server http client api.
NEO•ONE Server http client api.
Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js
Standards-compliant WebSocket server and client
WebSocket protocol handler with pluggable I/O
TypeScript client library for the Mistral AI API
A minimal node SOAP client
SockJS-node is a server counterpart of SockJS-client a JavaScript library that provides a WebSocket-like object in the browser. SockJS gives you a coherent, cross-browser, Javascript API which creates a low latency, full duplex, cross-domain communication
Offload tasks to a pool of workers on node.js and in the browser
An HTTP(s) proxy `http.Agent` implementation for HTTP
A simple zero-configuration command-line http server
LZ-based compression algorithm
HTTP proxying for the masses
Run MCP stdio servers over SSE, Streamable HTTP or visa versa
Cross Platform Smart Fetch Ponyfill
An RFC 3986/3987 compliant, scheme extendable URI/IRI parsing/validating/resolving library for JavaScript.
LiveReload JS client - auto reload browser on changes
AdonisJS HTTP server with support packed with Routing and Cookies
LangChain.js adapters for Model Context Protocol (MCP)
Reference implementation of Joyent's HTTP Signature scheme.
A browser polyfill for W3C EventSource (http://www.w3.org/TR/eventsource/)
SSH2 client and server modules written in pure JavaScript for node.js
Ruby library for talking to a one-wire server (see http://owfs.org)
Start a http server in any directory
Ruby library for talking to a one-wire server (see http://owfs.org)
API Batch adds batch call functionality to rails api's allowing a single batch http request to perform multiple api requests in one visit to the server.
This gem provides request authentication via [HMAC](http://en.wikipedia.org/wiki/Hmac). The main usage is request based, noninteractive authentication for API implementations. Two strategies are supported that differ mainly in how the authentication information is transferred to the server: One header-based authentication method and one query-based. The authentication scheme is in some parts based on ideas laid out in this article and the following discussion: http://broadcast.oreilly.com/2009/12/principles-for-standardized-rest-authentication.html The gem also provides a small helper class that can be used to generate request signatures.
ruby-xbmc is a ruby wrapper for the XBMC Web Server HTTP API. It provides a remote access to any XBMC running on the local network, in a simple way (methods follow the ones from XBMC API).
ruby-xbmc is a ruby wrapper for the XBMC Web Server HTTP API. It provides a remote access to any XBMC running on the local network, in a simple way (methods follow the ones from XBMC API).
Zokor is an HTTP proxy tunnelling tool that collapses multiple HTTP proxies into one. It's useful when you want to send traffic through a chain of two HTTP proxies where the first supports the CONNECT verb. Zokor presents a local server that transparently tunnels packets through the first proxy as though clients were directly connected to the second proxy. It optionally uses TLS to connect to the second proxy.
Em-resque is a version of Resque, which offers non-blocking and non-forking workers. The idea is to have fast as possible workers for tasks with lots of IO like pinging third party servers or hitting the database. The async worker is using fibers through Synchrony library to reduce the amount of callback functions. There's one fiber for worker and if one of the workers is blocking, it will block all the workers at the same time. The idea to use this version and not the regular Resque is to reduce the amount of SQL connections for high-load services. Using one process for many workers gives a better control to the amount of SQL connections. For using Resque please refer the original project. https://github.com/defunkt/resque/ The library adds two rake tasks over Resque: * resque:work_async for working inside the EventMachine
Companion gem for the Hyperion HTTP server. Patches PG::Connection so exec_params and friends cooperate with Async::Scheduler. Fibers serve other requests while one fiber waits on Postgres. Pure Ruby, drop-in.
Cartage provides a repeatable means to create a package for a server-side application that can be used in deployment with a configuration tool like Ansible, Chef, Puppet, or Salt. The package is created with vendored dependencies so that it can be deployed in environments with strict access control rules and without requiring development tool presence on the target server(s). This is the last release of cartage. It's been a fun ride, but Docker-based images are our future at Kinetic Commerce. There is one feature that remains useful, the release-metadata output. We have created a new, more extensible format for which we will be creating a gem to manage this. One example of the implementation can be found at: https://github.com/KineticCafe/release-metadata-ts We will also be replacing `cartage-rack` with a new gem supporting this new format.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.