Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
Subject: [PATCH] epoll+xepoll: clarify intent of these concurrency options
Date: Fri, 1 Mar 2013 23:33:44 +0000	[thread overview]
Message-ID: <20130301233344.GA2864@dcvr.yhbt.net> (raw)

Via private communication, I learned of a user using XEpoll
when he should not have been.
---
 Pushed to master of git://bogomips.org/rainbows

 lib/rainbows/epoll.rb  | 2 ++
 lib/rainbows/xepoll.rb | 2 ++
 2 files changed, 4 insertions(+)

diff --git a/lib/rainbows/epoll.rb b/lib/rainbows/epoll.rb
index a711186..4fbf9ba 100644
--- a/lib/rainbows/epoll.rb
+++ b/lib/rainbows/epoll.rb
@@ -19,6 +19,8 @@ require 'sendfile'
 # small enough to always be in your kernel page cache.  This concurrency
 # model may starve clients if you have slow disks and large static files.
 #
+# Do not use this if you have slow external dependencies.
+#
 # === RubyGem Requirements
 #
 # * raindrops 0.6.0 or later
diff --git a/lib/rainbows/xepoll.rb b/lib/rainbows/xepoll.rb
index a7f9d8c..1ba64f6 100644
--- a/lib/rainbows/xepoll.rb
+++ b/lib/rainbows/xepoll.rb
@@ -7,6 +7,8 @@ require 'rainbows/epoll'
 # for Ruby 1.9 users as it can avoid accept()-scalability issues on
 # multicore machines with many worker processes.
 #
+# Do not use this if you have slow external dependencies.
+#
 # === RubyGem Requirements
 #
 # * raindrops 0.6.0 or later
-- 
Eric Wong
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying


                 reply	other threads:[~2013-03-01 23:43 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=20130301233344.GA2864@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).