yahns Ruby server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: ruby-talk@ruby-lang.org, yahns-public@yhbt.net
Subject: [ANN] yahns 1.15.0 -_- sleepy app server for Ruby
Date: Thu, 23 Mar 2017 04:07:49 +0000	[thread overview]
Message-ID: <20170323040749.GA16820@dcvr> (raw)

A Free Software, multi-threaded, non-blocking network
application server designed for low _idle_ power consumption.
It is primarily optimized for applications with occasional users
which see little or no traffic.  yahns currently hosts Rack/HTTP
applications, but may eventually support other application
types.  Unlike some existing servers, yahns is extremely
sensitive to fatal bugs in the applications it hosts.

* git clone git://yhbt.net/yahns
* https://yhbt.net/yahns/README
* https://yhbt.net/yahns/NEWS.atom.xml (supported by most "RSS" readers)
* we only accept plain-text email yahns-public@yhbt.net
* and archive all the mail we receive: https://yhbt.net/yahns-public/
* nntp://news.public-inbox.org/inbox.comp.lang.ruby.yahns

lrg nabgure ubeevoyl-anzrq freire :>

Changes:

    yahns 1.15.0
    
    Minor changes to reduce allocations and simplify our code
    and dependencies.  Nothing particularly interesting unless
    you're the type of person who appreciates brake pedals
    in with holes drilled in them for weight reduction.
    
    11 changes since 1.14.1 (2016-12-14):
          stream_input: avoid allocation for common #read case
          proxy_pass: add a note about the instability of this
          tee_input: simplify conditional for writing to temporary file
          proxy_http_response: reduce memory pressure from larger headers
          http_response: make response headers eligible for GC, sooner
          update more referenced URLs to be HTTPS
          chunk_body: nodoc this internal class
          Revert "use olddoc 1.1.0 for generating NEWS + NEWS.atom.xml"
          gemspec: stop advertising "private" email address
          doc: design_notes: we do not use EPOLLEXCLUSIVE
          README: update with disclaimer about subscription
    
    Ovt punatrf pbzvat...

Please note the disclaimer:

  yahns is extremely sensitive to fatal bugs in the apps it hosts.  There
  is no (and never will be) any built-in "watchdog"-type feature to kill
  stuck processes/threads.  Each yahns process may be handling thousands
  of clients; unexpectedly killing the process will abort _all_ of those
  connections.  Lives may be lost!

  yahns hackers are not responsible for your application/library bugs.
  Use an application server which is tolerant of buggy applications
  if you cannot be bothered to fix all your fatal bugs.

-- 
EW

                 reply	other threads:[~2017-03-23  4:07 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/yahns/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170323040749.GA16820@dcvr \
    --to=e@80x24.org \
    --cc=ruby-talk@ruby-lang.org \
    --cc=yahns-public@yhbt.net \
    /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/yahns.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).