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: X-Spam-Status: No, score=-2.0 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00, URIBL_BLOCKED shortcircuit=no autolearn=unavailable version=3.3.2 X-Original-To: unicorn-public@bogomips.org Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 820261FB36; Tue, 5 Aug 2014 06:28:51 +0000 (UTC) Date: Tue, 5 Aug 2014 06:28:51 +0000 From: Eric Wong To: Gary Grossman Cc: hongli@phusion.nl, unicorn-public@bogomips.org, michael@grosser.it, mfischer@zendesk.com Subject: Re: Rack encodings (was: Please move to github) Message-ID: <20140805062851.GA5603@dcvr.yhbt.net> References: <818DDC4F-1D79-4290-8D02-9C1B4851D31D@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <818DDC4F-1D79-4290-8D02-9C1B4851D31D@gmail.com> List-Id: Gary Grossman wrote: > 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? Sure, rack-devel is a pretty dormant mailing list but there's been a burst of activity a few weeks ago. Unlike this list, subscription is required to post; and first posts from newbies are moderated. For folks who do not login to Google (crazies like me :P) subscription is possible without any login or password: rack-devel+subscribe@googlegroups.com > 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. At least there's other server implementers who'll probably chime in. > 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. Sounds like a good plan. Thanks for bringing more attention to this.