From: Eric Wong <e@80x24.org>
To: ruby-talk@ruby-lang.org
Cc: http_spew-public@bogomips.org
Subject: [ANN] http_spew 0.7.0 - LAN-only HTTP spam^H^H^H^Hclient for Ruby
Date: Tue, 13 Jun 2017 00:28:58 +0000 [thread overview]
Message-ID: <20170613-http_spew-0.7.0-released@bogomips.org> (raw)
This is not a new project, it's been public on RubyGems.org for
over 6 years, now, but I've been hesitant to announce it on
ruby-talk to a wider audience because... well, it's a bit nuts:
from the README and https://bogomips.org/http_spew/ ---
= HTTP Spew - LAN-only HTTP spam^H^H^H^Hclient for Ruby
Do not use HTTP Spew for connecting to servers outside of your LAN.
Do not use HTTP Spew without the permission of your server admins.
Use HTTP Spew if you wish you could kinda multicast with HTTP...
== Problems
* No support for bidirectional HTTP streaming
* No support for "Expect: 100-continue" headers/responses
* No support for DNS resolution (WONTFIX, ever)
* No support for HTTPS
* No support for keepalive (yet?)
* Not remotely RFC-compliant
* Messes up analytics/reporting on servers
* Resets server connections
* May get you banned from the Internet!
== Still Interested?
HTTP Spew lets you fire off identical (or similar) requests to multiple
HTTP servers and wait for any number (or all) of them to complete or for
a timeout to expire.
HTTP Spew may be useful for implementing reverse proxy servers if you
1) can't decide on a load balancing strategy for them
2) have much more hardware than you actually use
It's also completely untested and unused anywhere!
== Hacking
You can get the latest source via git from the following locations:
git://bogomips.org/http_spew.git
git://repo.or.cz/http_spew.git (mirror)
You may browse the code from the web and download the latest snapshot
tarballs here:
* https://bogomips.org/http_spew.git
* http://repo.or.cz/w/http_spew.git (gitweb)
Inline patches (from "git format-patch") to the mailing list are
preferred because they allow code review and comments in the reply to
the patch.
We will adhere to mostly the same conventions for patch submissions as
git itself. See the Documentation/SubmittingPatches document
distributed with git on on patch submission guidelines to follow. Just
don't email the git mailing list or maintainer with http_spew patches.
== Contact
All feedback (bug reports, user/development discussion, patches, pull
requests) go to the mailing list: mailto:http_spew-public@bogomips.org
Mailing list archives may be viewed and downloaded here:
https://bogomips.org/http_spew-public/
reply other threads:[~2017-06-13 0:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/http_spew/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170613-http_spew-0.7.0-released@bogomips.org \
--to=e@80x24.org \
--cc=http_spew-public@bogomips.org \
--cc=ruby-talk@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/http_spew.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox