From: ludo@gnu.org (Ludovic Courtès)
To: David Thompson <davet@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: Handling HTTP "Upgrade" requests
Date: Wed, 04 Mar 2015 11:51:54 +0100 [thread overview]
Message-ID: <87a8ztjar9.fsf@gnu.org> (raw)
In-Reply-To: <87wq3aan0s.fsf@fsf.org> (David Thompson's message of "Sat, 21 Feb 2015 18:00:03 -0500")
David Thompson <davet@gnu.org> skribis:
> I've been tinkering with adding WebSockets[0] support to Guile's HTTP
> arsenal. The first blocking issue I've come across is that an HTTP
> server must be able to detect the "Upgrade" header[1] and change
> protocols. In my case, once a client thread accepts a WebSocket
> connection, it should speak the WebSocket protocol, not HTTP.
Roughly, I would change ‘http-write’ in (web server http) to just remove
the socket from the server’s poll set when the response is an upgrade, no?
Ludo’.
prev parent reply other threads:[~2015-03-04 10:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 23:00 Handling HTTP "Upgrade" requests David Thompson
2015-02-25 5:05 ` Nala Ginrut
2015-02-25 16:23 ` Dave Thompson
2015-02-26 7:51 ` Nala Ginrut
2015-03-10 20:59 ` Andy Wingo
2015-03-11 3:55 ` Nala Ginrut
2015-03-04 10:51 ` Ludovic Courtès [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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8ztjar9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=davet@gnu.org \
--cc=guile-devel@gnu.org \
/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).