yahns Ruby server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: ruby-talk@ruby-lang.org, yahns-public@yhbt.net
Subject: [ANN] yahns 1.8.0 -_- sleepy app server for Ruby
Date: Thu, 11 Jun 2015 19:58:02 +0000	[thread overview]
Message-ID: <20150611-yahns-1.8.0-minor-updates-release@yhbt.net> (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.

minor updates

 Most notably, the Rack response body is now closed during rack.hijack.

   Middlewares such as Rack::Lock (used by Rails) break badly unless
   the response body is closed on hijack, so we will close it to follow
   the lead of other popular Rack servers.

   While it's unclear if there's anybody using rack.hijack besides
   yahns/proxy_pass we'll try to emulate the behavior of other servers
   as much as possible.

   ref: https://github.com/ngauthier/tubesock/issues/10

 We'll also support SIGWINCH if not daemonized

   This has no effect for the (default) single process case with
   no master/worker relationship as that does not support SIGWINCH.

  Some process managers such as foreman and daemontools rely on
  yahnsnot daemonizing, but we still want to be able to process
  SIGWINCH in that case.

  stdout and stderr may be redirected to a pipe (for cronolog or
  similar process), so those are less likely to be attached to a TTY
  than stdin.  This also allows users to process SIGWINCH when running
  inside a regular terminal if they redirect stdin to /dev/null.

  This follows unicorn commit a6077391bb62d0b13016084b0eea36b987afe8f0
  Thanks to Dan Moore for suggesting it on the unicorn list.

 A few more minor changes, more memory reduction changes coming...

 * proxy_pass: no point in closing StringIO
 * proxy_pass: allow filtering or overriding response headers
 * support SIGWINCH even if not daemonized
 * use Unicorn::HttpParser#response_start_sent accessor
 * reduce inline constant cache overheads
 * proxy_pass: skip tests if kcar is missing
 * ensure body is closed during hijack

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.

* git clone git://yhbt.net/yahns
* http://yahns.yhbt.net/README
* http://yahns.yhbt.net/NEWS.atom.xml
* we like plain-text email yahns-public@yhbt.net
* and archive all the mail we receive: http://yhbt.net/yahns-public/

-- 
EW

                 reply	other threads:[~2015-06-11 19:58 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=20150611-yahns-1.8.0-minor-updates-release@yhbt.net \
    --to=normalperson@yhbt.net \
    --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).