From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
Subject: per-client timeouts disabled in rainbows.git
Date: Mon, 12 Oct 2009 23:26:02 -0700 [thread overview]
Message-ID: <20091013062602.GA13128@dcvr.yhbt.net> (raw)
Since we can handle hundreds (if not thousands of concurrent clients),
per-process and spawn multiple processes, I think I'll leave those
timeouts disabled for now to keep the code simple.
Even if timeouts were enabled, it's still possible to write a simple
client that can keep a connection alive forever on end with periodic
requests...
I haven't seen a lot of idle/sleepy client attacks so I suspect
kiddies have better things to do than to DoS in this fashion.
Of course, the per-process timeout is still enabled in case your
app hits a blocking syscall/loop that freezes your entire process.
--
Eric Wong
reply other threads:[~2009-10-13 6:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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://yhbt.net/rainbows/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091013062602.GA13128@dcvr.yhbt.net \
--to=normalperson-rmlxzr9ms24@public.gmane.org \
--cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/rainbows.git/
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).