SCTP data channels in the browser
Node signaling server for the @web-udp/client package
Protocol library used in establishing connections between @web-udp/client peers
An abstract-encoding compliant module for encoding / decoding DNS packets
React Native UDP socket API for Android & iOS
The JavaScript implementation of the Multiaddr spec
Port of Log4js to work with node.
OpenTelemetry Exporter Jaeger allows user to send collected traces to Jaeger
A DNS Server and Client Implementation in Pure JavaScript with no dependencies.
Best-effort discovery of the machine's default gateway and local network IP exclusively with UDP sockets.
React-based UI component library implementing Fluent UI design for Univerus internal projects
An abstract-encoding compliant module for encoding / decoding DNS packets
Parse a magnet URI and return an object of keys/values
A nodejs module for local and remote Inter Process Communication (IPC), Neural Networking, and able to facilitate machine learning.
A simple parser/writer for the Session Description Protocol
Streaming torrent client
Establish UDP connections in the browser
Parse a magnet URI into an object
The Graylog Extended Log Format for the Node.js
Unity React Wrapped Stencil Components
A winston transport for UDP in typescript
An abstract-encoding compliant module for encoding / decoding DNS packets
Unified multi-protocol server runtime. One core, multiple transports.
UDP 公共包聚合 - 包含所有基础框架包
Ruby client which uses UDP to communicate with a daemon which uses HTTP POST to communicate with a Web server
Ruby client which uses UDP to communicate with a daemon which uses HTTP POST to communicate with a Web server
# holepunch [](http://badge.fury.io/rb/holepunch) [](https://travis-ci.org/undeadlabs/holepunch) Holepunch manages AWS EC2 security groups in a declarative way through a DSL. ## Requirements - Ruby 1.9.3 or newer. ## Installation ```bash gem install holepunch ``` or in your Gemfile ```ruby gem 'holepunch' ``` ## Basic Configuration You need to provide your AWS security credentials and a region. These can be provided via the command-line options, or you can use the standard AWS environment variables: ```bash export AWS_ACCESS_KEY_ID='...' export AWS_SECRET_ACCESS_KEY='...' export AWS_REGION='us-west-2' ``` ## The SecurityGroups file Specify your security groups in a `SecurityGroups` file in your project's root. Declare security groups that you need and the ingresses you want to expose. You can add ingresses using `tcp`, `udp`, and `ping`. For each ingress you can list allowed hosts using group names or CIDR notation. ```ruby group 'web' do desc 'Web servers' tcp 80 end group 'db' do desc 'database servers' tcp 5432, 'web' end group 'log' do desc 'log server' tcp 9999, 'web', 'db', '10.1.0.0/16' end ``` An environment can be specified which is available through the `env` variable. This allows you to have custom security groups per server environment. ```ruby group "#{env}-web" group "#{env}-db" do tcp 5432, "#{env}-web" end ``` Your application may depend on security groups defined by other services. Ensure they exist using the `depends` method. ```ruby depends 'my-other-service' group 'my-service' do udp 9999, 'my-other-service' end ``` You may specify port ranges for `tcp` and `udp` using the range operator. ```ruby group 'my-service' do udp 5000..9999, '0.0.0.0/0' end ``` You can specify ping/icmp rules with `icmp` (alias: `ping`). ```ruby group 'my-service' do ping '10.0.0.0/16' end ``` It can be useful to describe groups of security groups you plan to launch instances with by using the `service` declaration. ```ruby service "#{env}-web" do groups %W( admin #{env}-log-producer #{env}-web ) end ``` ## Usage Simply navigate to the directory containing your `SecurityGroups` file and run `holepunch`. ``` $ holepunch ``` If you need to specify an environment: ``` $ holepunch -e live ``` You can get a list of security groups for a service using the `service` subcommand. ``` $ holepunch service -e prod prod-web admin,prod-log-producer,prod-web ``` You can also get a list of all defined services. ``` $ holepunch service --list ``` ## Testing You can run the unit tests by simply running rspec. ``` $ rspec ``` By default the integration tests with EC2 are not run. You may run them with: ``` $ rspec -t integration ``` ## Authors - Ben Scott (gamepoet@gmail.com) - Pat Wyatt (pat@codeofhonor.com) ## License Copyright 2014 Undead Labs, LLC. Licensed under the MIT License: http://opensource.org/licenses/MIT
EventMachine-LE (Live Edition) is a branch of EventMachine (https://github.com/eventmachine/eventmachine). This branch incorporates interesting pull requests that are not yet included in the mainline EventMachine repository. The maintainers of that version prefer to minimize change in order to keep the stability with already existing EventMachine deployments, which provides an impressive multi-platform base for IPv4 TCP servers (e.g., Web servers) that don't need good UDP or IPv6 support. This dedication to stability is helpful for production use, but can also lead to ossification. The present "Live Edition" or "Leading Edge" branch has its focus on supporting a somewhat wider use, including new Web servers or protocols beyond the HTTP Web. To provide even more focus, this branch is currently applying its energy towards Linux and Unix/BSD/OSX environments. Java reactor and pure Ruby reactor are for now removed in this branch, and Windows/Cygwin support is untested. This may very well change later, once interesting pull requests come in. EventMachine-LE draws from a number of dormant pull requests on the mainline version of EventMachine. New proposals will also directly come to EventMachine-LE and will be included once they are tested. This is not a "development branch", EventMachine-LE is ready for production, just beyond the focus of mainline EventMachine.
HeapPeriscopeUi is a Rails engine designed to help developers monitor, visualize, and diagnose memory-related issues within their Ruby applications. It functions by listening for UDP packets containing GC profiler reports and heap snapshots, typically transmitted by a companion agent (like `heap_periscope_agent`). The engine efficiently processes this data: GC reports are batched for optimized database insertion, while comprehensive heap snapshots, including detailed object counts by class, are stored transactionally. Furthermore, HeapPeriscopeUi can broadcast incoming metrics via ActionCable for real-time dashboard updates. Its integrated web interface allows users to browse, filter, and analyze the collected profiler reports, facilitating the identification of memory leaks, excessive object allocations, and opportunities for performance optimization.
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.