From: Andy Wingo <wingo@pobox.com>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: Dave Thompson <davet@fsf.org>,
guile-devel@gnu.org, David Thompson <davet@gnu.org>
Subject: Re: Handling HTTP "Upgrade" requests
Date: Tue, 10 Mar 2015 21:59:00 +0100 [thread overview]
Message-ID: <87zj7ky3fv.fsf@pobox.com> (raw)
In-Reply-To: <1424937100.7013.37.camel@Renee-desktop.suse> (Nala Ginrut's message of "Thu, 26 Feb 2015 15:51:40 +0800")
On Thu 26 Feb 2015 08:51, Nala Ginrut <nalaginrut@gmail.com> writes:
> 3. I have to mention that the current inner server is not non-block and
> weak for slow-header-DDOS.
Indeed. I think the right solution is cothreads. What do you think?
> PS: To those who care, unfortunately, Guile has no epoll/kqueue yet,
> that's one of the reasons why I want to write new server core for
> Artanis. ;-)
The wip-ethreads branch has something like this. Perhaps that could
serve for inspiration :)
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2015-03-10 20:59 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 [this message]
2015-03-11 3:55 ` Nala Ginrut
2015-03-04 10:51 ` Ludovic Courtès
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=87zj7ky3fv.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=davet@fsf.org \
--cc=davet@gnu.org \
--cc=guile-devel@gnu.org \
--cc=nalaginrut@gmail.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).