From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Status: No, score=-2.2 required=3.0 tests=AWL,BAYES_00,FREEMAIL_FROM shortcircuit=no autolearn=unavailable version=3.3.2 X-Original-To: unicorn-public@bogomips.org Received: from mail-yh0-f46.google.com (mail-yh0-f46.google.com [209.85.213.46]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 701281FB58 for ; Tue, 5 Aug 2014 05:56:22 +0000 (UTC) Received: by mail-yh0-f46.google.com with SMTP id a41so331929yho.5 for ; Mon, 04 Aug 2014 22:56:20 -0700 (PDT) X-Received: by 10.236.100.171 with SMTP id z31mr2603136yhf.70.1407218180248; Mon, 04 Aug 2014 22:56:20 -0700 (PDT) Received: from [172.16.0.8] (108-67-145-4.lightspeed.sntcca.sbcglobal.net. [108.67.145.4]) by mx.google.com with ESMTPSA id v43sm1382968yhj.18.2014.08.04.22.56.18 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Aug 2014 22:56:19 -0700 (PDT) From: Gary Grossman Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Rack encodings (was: Please move to github) Date: Mon, 4 Aug 2014 22:56:18 -0700 Message-Id: <818DDC4F-1D79-4290-8D02-9C1B4851D31D@gmail.com> Cc: unicorn-public@bogomips.org, michael@grosser.it, e@80x24.org, mfischer@zendesk.com, gary.grossman@gmail.com To: hongli@phusion.nl Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) List-Id: It feels like we were getting some momentum here on an important but long-dormant issue here... maybe it's time to move this discussion to rack-devel? Perhaps there's another Rack luminary who can lead the charge, or at least see if there's some consensus after a few more years of shared experience on what "sane" encodings might look like. A lightweight way to move the implementation forward might be a simple Rack middleware gem which sets the new encodings on the environment, or adding the functionality to rack itself. Once developers were comfortable with the new regime, the app servers could follow suit and put those encodings in the env natively, and the Rubyland implementation of the new encodings could be dropped. Gary