From: Benjamin Wagener <bwagener@bwagener.de>
To: rack-devel@googlegroups.com
Subject: Re: teaching Rack to communicate over SPDY instead of HTTP
Date: Fri, 17 Jun 2011 08:43:59 +0200 [thread overview]
Message-ID: <4DFAF7AF.3020706@bwagener.de> (raw)
In-Reply-To: <4DFAF2E0.1040407@stormbrew.ca>
On 17.06.2011 08:23, Graham Batty wrote:
> Rack doesn't really speak any protocols. Rack is an API for interfacing
> server software with applications. In order to have a rack app 'speak'
> SPDY, all that needs to happen is for a Rack-capable server to be able
> to speak SPDY and appropriately call the application.
>
> In fact, in the Rack distribution there are already two non-HTTP
> protocol servers: CGI and FastCGI. SPDY is not really any different in
> nature than any of these. It supports some advanced features that would
> be difficult to work into the 1 request, 1 reply architecture of Rack,
> but even that's probably not insurmountable.
>
> There appears to already be a Rack SPDY server, btw:
> https://github.com/romanbsd/spdy
>
> I can't make any claims about how well it works, though. If you need
> this, you should probably give it a try.
>
> Graham.
Thank you very much for your suggestion. When I read the code of Rack I
saw so much HTTP-requests and so on that I thought it would be necessary
to change that for SPDY-compatibility. I also searched for already done
implementations of SPDY-server for Rails but only found the basic server
in ruby by Ilya Grigorik[1]. I will test the other server, but if there
is someone with some more suggestions for this subject, I would still
appreciate very much if you would share them with me.
Thanks again
Benjamin
[1]: https://github.com/igrigorik/spdy
prev parent reply other threads:[~2011-06-17 6:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 6:18 teaching Rack to communicate over SPDY instead of HTTP Benjamin Wagener
2011-06-17 6:23 ` Graham Batty
2011-06-17 6:43 ` Benjamin Wagener [this message]
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=4DFAF7AF.3020706@bwagener.de \
--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).