From: Tiago Cardoso <honeyryderchuck@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: HTTP2: Are we there yet?
Date: Fri, 15 Jan 2016 14:28:46 -0800 (PST) [thread overview]
Message-ID: <24c6a373-ff9a-452d-bcce-6adaac37d5ad@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1698 bytes --]
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.
[-- Attachment #1.2: Type: text/html, Size: 2056 bytes --]
next reply other threads:[~2016-01-15 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 22:28 Tiago Cardoso [this message]
2016-01-15 23:00 ` HTTP2: Are we there yet? James Tucker
2016-01-16 1:15 ` Eric Wong
2016-01-16 1:25 ` Aaron Patterson
2016-01-16 2:13 ` James Tucker
2016-08-09 3:02 ` Samuel Williams
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24c6a373-ff9a-452d-bcce-6adaac37d5ad@googlegroups.com \
--to=rack-devel@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
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).