From mboxrd@z Thu Jan 1 00:00:00 1970 Delivered-To: chneukirchen@gmail.com Received: by 10.25.18.86 with SMTP id h83csp745559lfi; Fri, 15 Jan 2016 14:41:53 -0800 (PST) X-Received: by 10.66.251.226 with SMTP id zn2mr18496319pac.44.1452897712923; Fri, 15 Jan 2016 14:41:52 -0800 (PST) Return-Path: Received: from mail-pa0-x23b.google.com (mail-pa0-x23b.google.com. [2607:f8b0:400e:c03::23b]) by mx.google.com with ESMTPS id tj2si16961596pab.76.2016.01.15.14.41.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Jan 2016 14:41:52 -0800 (PST) Received-SPF: pass (google.com: domain of rack-devel+bncBCFOBJU22UMRBL7L4W2AKGQEGH5DNPA@googlegroups.com designates 2607:f8b0:400e:c03::23b as permitted sender) client-ip=2607:f8b0:400e:c03::23b; Authentication-Results: mx.google.com; spf=pass (google.com: domain of rack-devel+bncBCFOBJU22UMRBL7L4W2AKGQEGH5DNPA@googlegroups.com designates 2607:f8b0:400e:c03::23b as permitted sender) smtp.mailfrom=rack-devel+bncBCFOBJU22UMRBL7L4W2AKGQEGH5DNPA@googlegroups.com; dkim=pass header.i=@googlegroups.com; dmarc=fail (p=NONE dis=NONE) header.from=gmail.com Received: by mail-pa0-x23b.google.com with SMTP id pv5sf40364113pac.1; Fri, 15 Jan 2016 14:41:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:message-id:subject:mime-version:content-type :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe; bh=/iEnos1oWzh0frVoZSatEkZMzkytaW34kXreWRhZbuk=; b=hTPDp+rKj6TKxqEIriN836YPmC/a6LX+p5OfjrfTrXi75ndW6uiq+pVq9rApNj59fm x+kipGZVgcIpQSSs1wu1vU5/KfXHKX1Z5zHGu69/xPtyWCJnXq+5OGWue0G162DPu7f1 10Waw2mxwexdqK3CxJmYFO4V/lkxqAe/vFZPRsOKSxobUkGaOIQr3nlbOKABI/BC1a/o S/owooG31/xfXdCt1ZAYf8rqNQm8nWcsPIHopJUFwXA2zADLxVwoFtXg0A7qOGISeyk/ R2FiPVWH2uOk9QzARXYebuk1npyqog/5MO2hgY0qW7es9ZwKrFyPYhYlvSugN+SLVrsW Kb/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:message-id:subject:mime-version :content-type:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe; bh=/iEnos1oWzh0frVoZSatEkZMzkytaW34kXreWRhZbuk=; b=nNVBVIoFHEknNvmE+BaY8RxnwzN/KcirFXRxhXRv9QIj7Y/InifiqTs/34lZXocyBp zbN6PErXKNlrDonrZ22USGTzqcuHl0htua5E67MiZoYVM3NYMyZak2LvkR0RXa3vjd3v /0/N3VNC5CfZg9/Rjq+8Lw0VfCsXuObZMkSEb8g7bDosMEGwdUjftWpSo7Qow3xkKSln et2ne7fHQ++7mIwD26firagAZhN9/tBzwDTsQBGj2jOpU0NVLWAJ42v1y5JlLpYSkV50 zMvzLvS3dz2L5IJsrGYQ/GSqCfRo1SBH0TTMapRopdxAG2HhZWtjyepfiSWpSk7MoYrW Dalg== X-Gm-Message-State: AG10YOTV51oaTxFaC1Zbqr3LLrGhP1fQp8SFnx1iFtRcAFMuh/rUd8hc7uhpglA1a0eb8Q== X-Received: by 10.50.114.163 with SMTP id jh3mr35482igb.1.1452897712058; Fri, 15 Jan 2016 14:41:52 -0800 (PST) X-BeenThere: rack-devel@googlegroups.com Received: by 10.107.148.134 with SMTP id w128ls983972iod.20.gmail; Fri, 15 Jan 2016 14:41:51 -0800 (PST) X-Received: by 10.66.101.4 with SMTP id fc4mr11163304pab.48.1452897711311; Fri, 15 Jan 2016 14:41:51 -0800 (PST) Received: by 10.50.57.73 with SMTP id g9msigq; Fri, 15 Jan 2016 14:28:47 -0800 (PST) X-Received: by 10.50.160.4 with SMTP id xg4mr34849igb.2.1452896927353; Fri, 15 Jan 2016 14:28:47 -0800 (PST) Date: Fri, 15 Jan 2016 14:28:46 -0800 (PST) From: Tiago Cardoso To: Rack Development Message-Id: <24c6a373-ff9a-452d-bcce-6adaac37d5ad@googlegroups.com> Subject: HTTP2: Are we there yet? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_965_273638145.1452896926877" X-Original-Sender: honeyryderChuck@gmail.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-Google-Group-Id: 486215384060 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , ------=_Part_965_273638145.1452896926877 Content-Type: multipart/alternative; boundary="----=_Part_966_143485006.1452896926877" ------=_Part_966_143485006.1452896926877 Content-Type: text/plain; charset=UTF-8 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, who's clearly been working in this. I think ruby needs http2 badly. I think that all other standards for pushing server-to-client/full-duplex/pipe-in-my-json will die after widespread adoption, like image spriting and all those HTTP1 performance "enhancements". I think that the ruby frameworks don't need and should not enforce websockets, specially for thing it was not designed for. I think ActionCable is crap. And just as Rails, I am entitled to an opinion, and would like to try to force it into people's throats. And I'd like to force http2 and consider myself a better human being after that. Only thing I found was this: https://groups.google.com/forum/#!topic/rack-devel/lipvWVZrcfo and after the author left the project. What's the status? Really appreciate any feedback, Tiago -- --- 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. ------=_Part_966_143485006.1452896926877 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi, I've been looking for developments in the rack fra= mework concerning its update towards great big http2. I've seen the pre= sentation 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.=C2=A0

I assume that http2 won't come with 2= .0 . Still, I'd like to know where we stand, what's missing for rac= k to develop further in that direction and where could I help/contribute. H= opefully there's a document someone can redirect me to.=C2=A0

I'm really looking forward to hearing from someone, pos= sibly Mr. Patterson, who's clearly been working in this. I think ruby n= eeds http2 badly. I think that all other standards for pushing server-to-cl= ient/full-duplex/pipe-in-my-json will die after widespread adoption, like i= mage spriting and all those HTTP1 performance "enhancements". I t= hink that the ruby frameworks don't need and should not enforce websock= ets, specially for thing it was not designed for. I think ActionCable is cr= ap. And just as Rails, I am entitled to an opinion, and would like to try t= o force it into people's throats. And I'd like to force http2 and c= onsider myself a better human being after that.

On= ly thing I found was this:=C2=A0https://groups.google.com/forum/#!topic/rac= k-devel/lipvWVZrcfo and after the author left the project. What's the s= tatus?

Really appreciate any feedback,
Tiago

--

---
You received this message because you are subscribed to the Google Groups &= quot;Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to rack-dev= el+unsubscribe@googlegroups.com.
For more options, visit http= s://groups.google.com/d/optout.
------=_Part_966_143485006.1452896926877-- ------=_Part_965_273638145.1452896926877--