Connect to a multi handle sublevel enabled db over http
Connect to a level-connect instance
Official library for using the Slack Platform's Socket Mode API
Request timeout middleware for Connect/Express
Low level library facilitating protocol buffers based communication with Trezor devices
Low-Level OAuth 2 / OpenID Connect Client API for JavaScript Runtimes
An API for using [DuckDB](https://duckdb.org/) in [Node](https://nodejs.org/).
TypeScript definitions for connect
Allow parsing of top-level await in modules
High-level javascript interface for Trezor hardware wallet.
The safe way to handle the `connect` socket event
High performance middleware framework
OpenTelemetry instrumentation for `connect` http middleware framework
e2e utilities for use with Playwright and Connect
## Local Development
Share an abstract-level database over the network or other kind of stream
Definitions of levels for logging purposes & shareable Symbol constants.
Turn a function into an `http.Agent` instance
Provides a fallback for non-existing directories so that the HTML 5 history API can be used.
Generates and consumes source maps
Node.js body parsing middleware
Detect whether a terminal supports color
A tool for connecting your design system components in code with your design system in Figma
Connect is a family of libraries for building and consuming APIs on different languages and platforms. [@connectrpc/connect](https://www.npmjs.com/package/@connectrpc/connect) brings type-safe APIs with Protobuf to TypeScript.
Allows for connection handling at the instance level.
This is a simple module-level registry for application globals. Use it to wrap global connection pools, memcached connections, redis, even database connections, and register them within a top-level namespace module of your application. For example, instead of doing Rails.cache you could be doing MyApp.rails_cache or MyApp.redis_cache, etc.
Rightscale::HttpConnection is a robust HTTP/S library. It implements a retry algorithm for low-level network errors. == FEATURES: - provides put/get streaming - does configurable retries on connect and read timeouts, DNS failures, etc. - HTTPS certificate checking
The FIX engine library allows one to easily connect to a FIX acceptor and establish a session, it will handle the administrative messages such as logons, hearbeats, gap fills and allow custom handling of business level messages. Likewise, an acceptor may be easily implemented by defining callbacks for business level messages. FIX protocol message parsing capabilities are provided by the fix-protocol gem, which currently supports the administrative subset (and a few business level messages) of the FIX 4.4 message specification.
Rightscale::HttpConnection is a robust HTTP/S library. It implements a retry algorithm for low-level network errors. == FEATURES: - provides put/get streaming - does configurable retries on connect and read timeouts, DNS failures, etc. - HTTPS certificate checking
== DESCRIPTION: The RightScale Slicehost gem has been designed to provide a robust interface to Slicehost's existing API. == FEATURES/PROBLEMS: - Full programmatic access to the Slicehost API. - Complete error handling: all operations check for errors and report complete error information by raising a SlicehostError. - Persistent HTTP connections with robust network-level retry layer using Rightscale::HttpConnection. This includes socket timeouts and retries. - Robust HTTP-level retry layer. Certain (user-adjustable) HTTP errors returned by Slicehost are classified as temporary errors. These errors are automaticallly retried using exponentially increasing intervals. The number of retries is user-configurable. == INSTALL:
== DESCRIPTION: The RightScale GoGrid gem has been designed to provide a robust interface to GoGrid's existing API. == FEATURES/PROBLEMS: - Full programmatic access to the GoGrid API. - Complete error handling: all operations check for errors and report complete error information by raising a GoGridError. - Persistent HTTP connections with robust network-level retry layer using RightHttpConnection). This includes socket timeouts and retries. - Robust HTTP-level retry layer. Certain (user-adjustable) HTTP errors returned by GoGrid are classified as temporary errors. These errors are automaticallly retried using exponentially increasing intervals. The number of retries is user-configurable.
The Internet Communications Engine (Ice) provides a robust, proven platform for developing mission-critical networked applications with minimal effort. Let Ice handle all of the low-level details such as network connections, serialization, and concurrency so that you can focus on your application logic. This package includes the Ice extension for Ruby, the standard Slice definition files, and the Slice-to-Ruby compiler. You will need to install a full Ice distribution if you want to use other Ice language mappings, or Ice services such as IceGrid, IceStorm and Glacier2. We provide extensive online documentation for Ice, the Ruby extension, and the other Ice language mappings and servicespec. Join us on our user forums if you have questions about Ice.
The Internet Communications Engine (Ice) provides a robust, proven platform for developing mission-critical networked applications with minimal effort. Let Ice handle all of the low-level details such as network connections, serialization, and concurrency so that you can focus on your application logic. This package includes the Ice extension for Ruby, the standard Slice definition files, and the Slice-to-Ruby compiler. You will need to install a full Ice distribution if you want to use other Ice language mappings, or Ice services such as IceGrid, IceStorm and Glacier2. We provide extensive online documentation for Ice, the Ruby extension, and the other Ice language mappings and services. Join us on our user forums if you have questions about Ice.
The Internet Communications Engine (Ice) provides a robust, proven platform for developing mission-critical networked applications with minimal effort. Let Ice handle all of the low-level details such as network connections, serialization, and concurrency so that you can focus on your application logic. This package includes the Ice extension for Ruby, the standard Slice definition files, and the Slice-to-Ruby compiler. You will need to install a full Ice distribution if you want to use other Ice language mappings, or Ice services such as IceGrid, IceStorm and Glacier2. We provide extensive online documentation for Ice, the Ruby extension, and the other Ice language mappings and services. Join us on our user forums if you have questions about Ice.
RSence is a different and unique development model and software frameworks designed first-hand for real-time web applications. RSence consists of separate, but tigtly integrated data- and user interface frameworks. RSence could be classified as a thin server - thick client system. Applications and submobules are installed as indepenent plugin bundles into the plugins folder of a RSence environment, which in itself is a self-contained bundle. A big part of RSence itself is implemented as shared plugin bundles. The user interface framework of RSence is implemented in high-level user interface widget classes. The widget classes share a common foundation API and access the browser's native API's using an abstracted event- and element layer, which provides exceptional cross-browser compatibility. The data framework of RSence is a event-driven system, which synchronized shared values between the client and server. It's like a realtime bidirectional form-submission engine that handles data changes intelligently. On the client, changed values trigger events on user interface widgets. On the server, changed values trigger events on value responder methods of server plugin modules. It doesn't matter if the change originates on client or server, it's all synchronized and propagated automatically. The server framework is implemented as a high-level, modular data-event-driven system, which handles delegation of tasks impossible to implement using a client-only approach. Client sessions are selectively connected to other client sessions and legacy back-ends via the server by using the data framework. The client is written in Javascript and the server is written in Ruby. The client also supports CoffeeScript for custom logic. In many cases, no custom client logic is needed; the user interfaces can be defined in tree-like data models. By default, the models are parsed from YAML files, and other structured data formats are possible, including XML, JSON, databases or any custom logic capable of producing similar objects. The server can connect to custom environments and legacy backends accessible on the server, including software written in other languages.
RSence is a different and unique development model and software frameworks designed first-hand for real-time web applications. RSence consists of separate, but tigtly integrated data- and user interface frameworks. RSence could be classified as a thin server - thick client system. Applications and submobules are installed as indepenent plugin bundles into the plugins folder of a RSence environment, which in itself is a self-contained bundle. A big part of RSence itself is implemented as shared plugin bundles. The user interface framework of RSence is implemented in high-level user interface widget classes. The widget classes share a common foundation API and access the browser's native API's using an abstracted event- and element layer, which provides exceptional cross-browser compatibility. The data framework of RSence is a event-driven system, which synchronized shared values between the client and server. It's like a realtime bidirectional form-submission engine that handles data changes intelligently. On the client, changed values trigger events on user interface widgets. On the server, changed values trigger events on value responder methods of server plugin modules. It doesn't matter if the change originates on client or server, it's all synchronized and propagated automatically. The server framework is implemented as a high-level, modular data-event-driven system, which handles delegation of tasks impossible to implement using a client-only approach. Client sessions are selectively connected to other client sessions and legacy back-ends via the server by using the data framework. The client is written in Javascript and the server is written in Ruby. The client also supports CoffeeScript for custom logic. In many cases, no custom client logic is needed; the user interfaces can be defined in tree-like data models. By default, the models are parsed from YAML files, and other structured data formats are possible, including XML, JSON, databases or any custom logic capable of producing similar objects. The server can connect to custom environments and legacy backends accessible on the server, including software written in other languages.
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.