yahns Ruby server user/dev discussion
 help / color / Atom feed
From: Eric Wong <e@80x24.org>
To: ruby-talk@ruby-lang.org
Cc: yahns-public@yhbt.net
Subject: [ANN] yahns 1.14.1 -_- sleepy app server for Ruby
Date: Wed, 14 Dec 2016 19:23:42 +0000
Message-ID: <20161214-yahns-1.14.1-released@YHBT.net> (raw)
In-Reply-To: <20161114-yahns-1.14.0-released@YHBT.net>

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.14.1 - bugfixes only

    This release avoids confusing HTTP/1.1 clients with a
    "Transfer-Encoding: chunked" header on bodyless responses.
    The header was causing "curl -T" to wait indefinitely for
    a response body after the server sent a 204.
    This regression was introduced with autochunk introduced
    with yahns 1.13(*).

    rack.hijack was also broken for ancient "HTTP/0.9" requests,
    and now fixed.

    4 changes since 1.14.0:

          queue_*: fix outdated comments
          http_response: support rack.hijack on HTTP/0.9 responses
          response: do not set chunked header on bodyless responses
          proxy_pass: do not chunk on bodyless upstream responses

    (*) https://yhbt.net/yahns-public/20160805-yahns-1.13.0-released@lucky13/

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 index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14 21:22 [ANN] yahns 1.14.0 " Eric Wong
2016-12-14 19:23 ` Eric Wong [this message]

Reply instructions:

You may reply publically 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=20161214-yahns-1.14.1-released@YHBT.net \
    --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

yahns Ruby server user/dev discussion

Archives are clonable:
	git clone --mirror https://yhbt.net/yahns-public
	git clone --mirror http://ou63pmih66umazou.onion/yahns-public

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.lang.ruby.yahns
	nntp://ou63pmih66umazou.onion/inbox.comp.lang.ruby.yahns

 note: .onion URLs require Tor: https://www.torproject.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox