From: "Mark J. Titorenko" <mark.titorenko-82pbMkz6NcNsbIuE7sb01tBPR1lH4CV8@public.gmane.org>
To: "rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org"
<rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org>
Subject: [PATCH] event_machine: join reactor_thread if it is already running rather than falling through worker_loop
Date: Fri, 11 Jan 2013 11:57:12 +0000 [thread overview]
Message-ID: <F24725C0-EE29-4AA0-85C3-8E0A756EB9F9@gmail.com> (raw)
Prior to the application of this patch, if an EventMachine reactor_thread has already been started elsewhere before the worker_loop is entered, the worker_loop exits as a second call to EM.run does not block the current thread.
This patch causes the worker_loop thread to join the reactor_thread if it is running.
Cheers,
Mark.
---
lib/rainbows/event_machine.rb | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/rainbows/event_machine.rb b/lib/rainbows/event_machine.rb
index 3ecdb4f..b143b39 100644
--- a/lib/rainbows/event_machine.rb
+++ b/lib/rainbows/event_machine.rb
@@ -99,6 +99,7 @@ module Rainbows::EventMachine
end
end
}
+ EM.reactor_thread.join if EM.reactor_running?
end
end
# :enddoc:
--
1.7.9.6 (Apple Git-31.1)
_______________________________________________
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
next reply other threads:[~2013-01-11 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 11:57 Mark J. Titorenko [this message]
[not found] ` <F24725C0-EE29-4AA0-85C3-8E0A756EB9F9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-01-11 20:18 ` [PATCH] event_machine: join reactor_thread if it is already running rather than falling through worker_loop Eric Wong
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=F24725C0-EE29-4AA0-85C3-8E0A756EB9F9@gmail.com \
--to=mark.titorenko-82pbmkz6ncnsbiue7sb01tbpr1lh4cv8@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).