From mboxrd@z Thu Jan 1 00:00:00 1970 Delivered-To: chneukirchen@gmail.com Received: by 10.25.18.86 with SMTP id h83csp800772lfi; Fri, 15 Jan 2016 17:25:46 -0800 (PST) X-Received: by 10.66.140.79 with SMTP id re15mr18696049pab.127.1452907546799; Fri, 15 Jan 2016 17:25:46 -0800 (PST) Return-Path: Received: from mail-pf0-x23d.google.com (mail-pf0-x23d.google.com. [2607:f8b0:400e:c00::23d]) by mx.google.com with ESMTPS id h3si16549588pfd.89.2016.01.15.17.25.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Jan 2016 17:25:46 -0800 (PST) Received-SPF: pass (google.com: domain of rack-devel+bncBDI5L5VXVAHBBGVY422AKGQE2QM5III@googlegroups.com designates 2607:f8b0:400e:c00::23d as permitted sender) client-ip=2607:f8b0:400e:c00::23d; Authentication-Results: mx.google.com; spf=pass (google.com: domain of rack-devel+bncBDI5L5VXVAHBBGVY422AKGQE2QM5III@googlegroups.com designates 2607:f8b0:400e:c00::23d as permitted sender) smtp.mailfrom=rack-devel+bncBDI5L5VXVAHBBGVY422AKGQE2QM5III@googlegroups.com; dkim=pass header.i=@googlegroups.com Received: by mail-pf0-x23d.google.com with SMTP id q63sf58674533pfb.0; Fri, 15 Jan 2016 17:25:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=sender:date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=zpeRgyttbcOfcu3fMSJkA1MaEgh5SVsg7wRtD7lom3k=; b=o/44F+7/tq96YAZ+irHq6kGedgGa0Ag0ZdCn0uOYYWheFJiAFXkUJcAB7N5yMm7JG4 7YYvT5+vCI/7Du3uZNQexB+eq5CePWZu1L4U7Ey7U/ueHszJRecvJ+tIT1gk0Wutpm47 xM5vVJwIN9vUUcS4Hdde1Y36NVBBbpoMnTlg7tFHz22luAz3mJ6NuTwQvzl+ELXFFjmj TkyFhes7dK6eOCYZStaw0Dzb5w2LFXtekmBoLFkXVICY9psr10IewtTIVUJ6fwrWenDu LjPWkiiB0TrvGHhbxaR04s0Z/GeVFC6TSKmWwcD3IGKkkH/GWG+PWK04KSoBdBO3+f5C nZqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:subject:message-id :references:mime-version:content-type:content-disposition :in-reply-to:user-agent:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=zpeRgyttbcOfcu3fMSJkA1MaEgh5SVsg7wRtD7lom3k=; b=c5QSHghAU04ibgNq1H9BSfdce0eWHVc1pW8Rj2oqjdKG6tjjZNvQV5XnwtzoXqJzAG enEDhVS6e6ZiTQ+Okw9Jfo+MgAbsbcv61AcZNg2OhHhA+d8MUHz0MIDVifpyVBoscIeL TNP9wffgeVNvn4hu2lcIC3IsGnbRMsNP1B25AZtbQr5G8MdFTXZvU0exoGwwmMObvFDY X8bZPPOhgEx2KlAMwbvzurMgXgEqXTQcnXGIrdjs9oqvfEOlXHTyFdj9LMWE8JOoZbku geDgbUBspsQVW5J2MJS0OaSjzDFxmEgAl4tIBk5JmzFmqAdMUgZ1orzLC2XiPSWOG/96 39MQ== X-Gm-Message-State: AG10YOSGIFVJPR5yjDyJmNqpAztIiZ60IU80r6Mj75Ma25tTG3z9o/RIT8YLlF3pU0o9Fg== X-Received: by 10.50.3.73 with SMTP id a9mr47390iga.4.1452907546415; Fri, 15 Jan 2016 17:25:46 -0800 (PST) X-BeenThere: rack-devel@googlegroups.com Received: by 10.50.50.139 with SMTP id c11ls314536igo.38.canary; Fri, 15 Jan 2016 17:25:45 -0800 (PST) X-Received: by 10.66.121.132 with SMTP id lk4mr11468385pab.7.1452907545860; Fri, 15 Jan 2016 17:25:45 -0800 (PST) Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com. [2607:f8b0:400e:c00::236]) by gmr-mx.google.com with ESMTPS id i25si1020304pfj.2.2016.01.15.17.25.45 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Jan 2016 17:25:45 -0800 (PST) Received-SPF: neutral (google.com: 2607:f8b0:400e:c00::236 is neither permitted nor denied by best guess record for domain of aaron@tenderlovemaking.com) client-ip=2607:f8b0:400e:c00::236; Received: by mail-pf0-x236.google.com with SMTP id e65so126336358pfe.0 for ; Fri, 15 Jan 2016 17:25:45 -0800 (PST) X-Received: by 10.98.0.66 with SMTP id 63mr13592522pfa.61.1452907545674; Fri, 15 Jan 2016 17:25:45 -0800 (PST) Received: from TC.local (c-24-56-229-227.customer.broadstripe.net. [24.56.229.227]) by smtp.gmail.com with ESMTPSA id p66sm18010311pfi.34.2016.01.15.17.25.44 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Jan 2016 17:25:44 -0800 (PST) Sender: rack-devel@googlegroups.com Date: Fri, 15 Jan 2016 17:25:42 -0800 From: Aaron Patterson To: rack-devel@googlegroups.com Subject: Re: HTTP2: Are we there yet? Message-ID: <20160116012542.GA77422@TC.local> References: <24c6a373-ff9a-452d-bcce-6adaac37d5ad@googlegroups.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline In-Reply-To: <24c6a373-ff9a-452d-bcce-6adaac37d5ad@googlegroups.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-Original-Sender: aaron@tenderlovemaking.com X-Original-Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 2607:f8b0:400e:c00::236 is neither permitted nor denied by best guess record for domain of aaron@tenderlovemaking.com) smtp.mailfrom=aaron@tenderlovemaking.com Reply-To: rack-devel@googlegroups.com Precedence: list Mailing-list: list rack-devel@googlegroups.com; contact rack-devel+owners@googlegroups.com List-ID: X-Spam-Checked-In-Group: rack-devel@googlegroups.com X-Google-Group-Id: 486215384060 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline On Fri, Jan 15, 2016 at 02:28:46PM -0800, Tiago Cardoso wrote: > Hi, I've been looking for developments in the rack framework concerning its > update towards great big http2. I've seen the presentation from Aaron > Patterson from October/November, and since then, only seen the events > middleware landing in master. And there's an alpha 2.0 version. > > I assume that http2 won't come with 2.0 . Still, I'd like to know where we > stand, what's missing for rack to develop further in that direction and > where could I help/contribute. Hopefully there's a document someone can > redirect me to. > > I'm really looking forward to hearing from someone, possibly Mr. Patterson, Right now, my rough plan is: Add a new key / value pair to the env hash where the value is an object that, when called, does server push. The webserver is responsible for implementing what that means (my current experiments will re-issue a request to the app server, so the application can't tell the difference between a request that originated from a browser vs a request that originated from a push). This will give us server push (which is the only thing that h2 does differently than h1 from Rack's perspective) while maintaining backwards compatibility. Probably Rack 3 will diverge from hashes everywhere, but this should work for now. Other stuff that h2 does, like keeping the connection alive, header compression, etc isn't Rack's concern. -- Aaron Patterson http://tenderlovemaking.com/ -- --- You received this message because you are subscribed to the Google Groups "Rack Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/d/optout. --wRRV7LY7NUeQGEoC Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJWmZwWAAoJEJUxcLy0/6/GmdsH/i0jjrtfEO5k9mKCiVS1E+ju u4ByO364r4t2Odg+zuvs13GtggT+AsxNdJd2Xdf2l0fa6Gh1SIGG3C/f0q1XjhFl zxLSjc5AdSWVaW4jw559zy6BANCaWZv+OxboYWG2RL5TKPmzt7FiOny6dA+W71Cw 56xpBskKqjDD45K4QvkyiOBIqs7C4GBcihe98HV9L3x2OKxfH9ZdnZAtc2deh05C YYIDWLw8nppsKVmLNCrfTCf8uCcNzC6FxNh3TpbE+KnfiRDw2LCuVrwP/RjF1uyW VJSRlXPUlCjGCQ77jo+X33VVsXF62ETjn5Yjx6ZYiI3GHdQwtTLSSMnvgRbWy/4= =+i65 -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC--