From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-0.5 required=5.0 tests=AWL,MSGID_FROM_MTA_HEADER, RP_MATCHES_RCVD shortcircuit=no autolearn=unavailable version=3.3.2 Path: news.gmane.org!not-for-mail From: Eric Wong Newsgroups: gmane.comp.lang.ruby.general,gmane.comp.lang.ruby.unicorn.general Subject: [ANN] unicorn 1.0.0 - yes, this is a real project Date: Thu, 17 Jun 2010 19:08:29 +0900 Organization: scary devil \m/onastery Message-ID: <20100617100825.GA17552@dcvr.yhbt.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1276769352 29096 80.91.229.12 (17 Jun 2010 10:09:12 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 17 Jun 2010 10:09:12 +0000 (UTC) To: ruby-talk@ruby-lang.org (ruby-talk ML) ,mongrel-unicorn@rubyforge.org Original-X-From: ruby-talk-admin@ruby-lang.org Thu Jun 17 12:09:10 2010 Return-path: Envelope-to: gclrg-ruby-talk@m.gmane.org Delivered-To: ruby-talk@ruby-lang.org Original-Posted: Thu, 17 Jun 2010 10:08:25 +0000 X-ML-Name: ruby-talk X-Mail-Count: 364497 X-MLServer: fml [fml 4.0.3 release (20011202/4.0.3)]; post only (only members can post) X-ML-Info: If you have a question, send e-mail with the body "help" (without quotes) to the address ruby-talk-ctl@ruby-lang.org; help= User-Agent: Mutt/1.5.18 (2008-05-17) Content-Disposition: inline X-Subject-2: and an experiment! (a marketing experiment, actually) Precedence: bulk Original-Lines: 50 List-Id: List-Software: fml [fml 4.0.3 release (20011202/4.0.3)] List-Post: List-Owner: List-Help: List-Unsubscribe: Xref: news.gmane.org gmane.comp.lang.ruby.general:321590 gmane.comp.lang.ruby.unicorn.general:585 Archived-At: Received: from carbon.ruby-lang.org ([221.186.184.68]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OPC21-0006Kd-JY for gclrg-ruby-talk@m.gmane.org; Thu, 17 Jun 2010 12:09:10 +0200 Received: from carbon.ruby-lang.org (beryllium.ruby-lang.org [127.0.0.1]) by carbon.ruby-lang.org (Postfix) with ESMTP id 211373C22729C; Thu, 17 Jun 2010 19:08:35 +0900 (JST) Received: from dcvr.yhbt.net (dcvr.yhbt.net [64.71.152.64]) by carbon.ruby-lang.org (Postfix) with ESMTP id 027883C21F73A for ; Thu, 17 Jun 2010 19:08:29 +0900 (JST) Received: from localhost (unknown [127.0.2.5]) by dcvr.yhbt.net (Postfix) with ESMTP id 56F7B1F488; Thu, 17 Jun 2010 10:08:25 +0000 (UTC) Unicorn is an HTTP server for Rack applications designed to only serve fast clients on low-latency, high-bandwidth connections and take advantage of features in Unix/Unix-like kernels. Slow clients should only be served by placing a reverse proxy capable of fully buffering both the the request and response in between Unicorn and slow clients. * http://unicorn.bogomips.org/ * mongrel-unicorn@rubyforge.org * git://git.bogomips.org/unicorn.git Changes: There are only minor changes since 0.991.0. For users clinging onto the past, MRI 1.8.6 support has been restored. Users are strongly encouraged to upgrade to the latest 1.8.7, REE or 1.9.1. For users looking towards the future, the core test suite and the Rails 3 (beta) integration tests pass entirely under 1.9.2 preview3. As of the latest rubinius.git[1], Rubinius support is nearly complete as well. Under Rubinius, signals may corrupt responses as they're being written to the socket, but that should be fixable transparently to us[4]. Support for the hardly used, hardly documented[2] embedded command-line switches in rackup config (.ru) files is is also broken under Rubinius. The recently-released Rack 1.2.1 introduced no compatiblity issues[3] in core Unicorn. We remain compatible with all Rack releases starting with 0.9.1 (and possibly before). [1] tested with Rubinius upstream commit cf4a5a759234faa3f7d8a92d68fa89d8c5048f72 [2] lets avoid the Dueling Banjos effect here :x [3] actually, Rack 1.2.1 is broken under 1.8.6. [4] http://github.com/evanphx/rubinius/issues/373 The Future: * Bug/compatibility fixes as needed, of course! * Scalability for hardware that may be common in 5-10 years * Rainbows! LOTS of Rainbows! Thanks for reading! -- Eric Wong