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.12.4 -_- sleepy app server for Ruby
Date: Mon, 2 May 2016 19:47:15 +0000	[thread overview]
Message-ID: <20160502-yahns-1.12.4-unle@shed> (raw)
In-Reply-To: <20160408-yahns-1.12.3-unle@shed>

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://yahns.yhbt.net/README
* https://yahns.yhbt.net/NEWS.atom.xml
* 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


    yahns 1.12.4 - rack.hijack and proxy_pass bugfixes

    This release fixes some resource leaks in uncommonly used parts
    of yahns as well as including some documentation improvements.
    No need to upgrade unless you rely on rack.hijack for responses
    or use the (currently-undocumented) proxy_pass module(*).

    9 non-merge changes since 1.12.3:

          proxy_pass: honor wbuf_persist when ending response
          proxy_http_response: fix non-terminated fast responses, too
          test_proxy_pass: test for auto chunking on 1.0 backends
          wbuf: drop persistence if writing to client fails
          proxy_http_response: cleanup: avoid redundant setting of "alive"
          proxy_http_response: do not persist upstream on slow clients
          proxy_pass: drop resources immediately on errors
          document Rack::Chunked/ContentLength semi-requirements
          extras/exec_cgi: document cgit example

     Documentation/yahns-rackup.pod    | 10 ++++++++++
     GIT-VERSION-GEN                   |  2 +-
     examples/yahns_rack_basic.conf.rb |  6 ++++++
     extras/exec_cgi.rb                |  8 ++++++++
     lib/yahns/proxy_http_response.rb  | 40 ++++++++++++++++++++++-----------------
     lib/yahns/proxy_pass.rb           |  5 +++--
     lib/yahns/wbuf_common.rb          |  1 +
     test/test_proxy_pass.rb           | 15 +++++++++++++++
     8 files changed, 67 insertions(+), 20 deletions(-)

    (*) 1.13.0 will include refactoring in proxy_pass and possibly
        documenting it as stable-enough-for-public use:


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.

  reply	other threads:[~2016-05-02 19:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-08 20:01 [ANN] yahns 1.12.3 -_- sleepy app server for Ruby Eric Wong
2016-05-02 19:47 ` Eric Wong [this message]
2016-06-05 23:12   ` [ANN] yahns 1.12.5 " Eric Wong

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:

  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=20160502-yahns-1.12.4-unle@shed \
    --to=normalperson@yhbt.net \
    --cc=ruby-talk@ruby-lang.org \
    --cc=yahns-public@yhbt.net \


* 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


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).