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.6.0 -_- sleepy app server for Ruby
Date: Mon, 9 Mar 2015 09:49:03 +0000	[thread overview]
Message-ID: <20150309094903.GA25761@dcvr.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.

Changes: reduced allocations and bugfixes

  This release fixes a bug where previously-configured-but-now-removed
  listeners were inherited across USR2 upgrades are not shutdown
  immediately in the child.

  There are also minor reductions in allocations which can save a few
  hundred bytes statically and also whenever write buffering is necessary
  for large responses.

  Some minor documentation updates improvements in extras, too.

  shortlog of changes since 1.5.0:
      README: add link to mailing list archives
      test_ssl: factor out server SSLContext creation
      doc: add design_notes document
      reduce File::Stat object allocations
      update comments about wbuf_close return values
      wbuf: lazily (re)create temporary file
      fix compatibility with unicorn.git
      skip tests requiring String#b on 1.9.3
      use the monotonic clock under Ruby 2.1+
      favor Class.new for method-less classes
      extras/proxy_pass: save memory in String#split arg
      extras/proxy_pass: do not name unused variable
      extras/proxy_pass: log exceptions leading to 502
      extras/proxy_pass: flesh out upload support + tests
      acceptor: close inherited-but-unneeded sockets

  See the git repository for more: git clone git://yhbt.net/yahns

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/

lrg nabgure ubeevoyl-anzrq freire
lrf, lnuaf vf frys-ubfgvat vgf bja fvgrf fvapr yngr 2013

                 reply	other threads:[~2015-03-09  9:49 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=20150309094903.GA25761@dcvr.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).