[ANN] yahns 1.7.0 -_- sleepy app server for Ruby

[ANN] yahns 1.7.0 -_- sleepy app server for Ruby

[Eric Wong]

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: rack.hijack improvements and more

    Nothing really significant, so there's no need to upgrade if
    you're not affected by the minor fixes and changes in this
    release.

    For all users, LoadError and SyntaxError exceptions are now
    logged and non-fatal within worker threads serving application
    code.  Thanks to Lin Jen-Shin <godfat@godfat.org> for bringing
    this up on the mailing list.

    Additionally, temporary files buffered to the filesystem will
    now support the Rack::TempfileReaper middleware in rack 1.6+

    For rack.hijack users, there are some changes and improvements.
    rack.hijack should return a usable IO-like object for SSL users,
    now.  The rack.input object is no longer closed on hijacking,
    allowing apps to continue using buffered input after hijacking.
    There is also a bugfix for the rare apps which hijack requests
    after emitting 100-continue responses.

    Note: there is also a work-in-progress and under-documented
    asynchronous Yayns::ProxyPass Rack app which uses rack.hijack
    internally.  This will allow yahns to act as a fully-buffering
    reverse proxy to upstream servers which cannot handle slow
    clients.  Yahns::ProxyPass NOT production-ready as of this
    release.  The old, synchronous extras/proxy_pass.rb code
    remains usable.

    There's also the usual round of minor code bloat reduction.

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/