unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Gary Grossman <gary.grossman@gmail.com>
To: hongli@phusion.nl
Cc: unicorn-public@bogomips.org, michael@grosser.it, e@80x24.org,
	mfischer@zendesk.com, gary.grossman@gmail.com
Subject: Re: Rack encodings (was: Please move to github)
Date: Mon, 4 Aug 2014 22:56:18 -0700	[thread overview]
Message-ID: <818DDC4F-1D79-4290-8D02-9C1B4851D31D@gmail.com> (raw)

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


             reply	other threads:[~2014-08-05  5:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05  5:56 Gary Grossman [this message]
2014-08-05  6:28 ` Rack encodings (was: Please move to github) Eric Wong
  -- strict thread matches above, loose matches on Subject: below --
2014-08-02  7:51 Please move to github Gary Grossman
2014-08-02  8:50 ` Eric Wong
2014-08-02 19:07   ` Gary Grossman
2014-08-02 19:33     ` Michael Fischer
2014-08-04  7:22       ` Hongli Lai
2014-08-04  8:48         ` Rack encodings (was: Please move to github) Eric Wong
2014-08-04  9:46           ` Hongli Lai

Reply instructions:

You may reply publicly 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:

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=818DDC4F-1D79-4290-8D02-9C1B4851D31D@gmail.com \
    --to=gary.grossman@gmail.com \
    --cc=e@80x24.org \
    --cc=hongli@phusion.nl \
    --cc=mfischer@zendesk.com \
    --cc=michael@grosser.it \
    --cc=unicorn-public@bogomips.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).