From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Thread.current
Date: Tue, 11 Jan 2011 15:12:27 -0800 [thread overview]
Message-ID: <20110111231227.GA27058@dcvr.yhbt.net> (raw)
In-Reply-To: <AANLkTim=ymsUHz8KN5niEV6kwJaMtOQyuMny-CqDSqgb@mail.gmail.com>
Jimmy Soho <jimmy.soho@gmail.com> wrote:
> Hi,
>
> Some more questions still:
>
> It seems a worker uses the exact same thread to handle each request.
Correct.
> Is that guaranteed to happen for the lifetime of a worker? Or are
> there cases where a unicorn worker might spin a new thread to handle
> the next requests?
Unicorn itself is always single-threaded and never spawns new threads.
> If the same thread is always used, isn't that a potential issue when
> programmers use thread local variables, which are not reset at the
> next request? (I know, the usage of thread local variables is not
> recommended, but take a random rails project, go into their $GEM_HOME
> and do grep -r Thread.current . , see what I mean..)
Thats the problem of those libraries/apps, not Unicorn.
They can try Rainbows! using the :ThreadSpawn option which behaves much
like Mongrel 1, but uses Rainbows! in production that I know of.
The Rack +env+ hash is the safe/universal way to store request-local
variables across different web servers.
--
Eric Wong
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2011-01-11 23:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 2:00 Thread.current Jimmy Soho
2011-01-08 2:57 ` Thread.current Eric Wong
2011-01-08 3:09 ` Thread.current Curtis j Schofield
2011-01-08 5:54 ` Thread.current Jimmy Soho
2011-01-11 22:52 ` Thread.current Jimmy Soho
2011-01-11 23:12 ` Eric Wong [this message]
2011-01-11 23:12 ` Thread.current Jordan Ritter
2011-01-12 3:07 ` Thread.current Jimmy Soho
2011-01-13 4:26 ` Thread.current Eric Wong
2011-01-13 16:46 ` Thread.current Jordan Ritter
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/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110111231227.GA27058@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=mongrel-unicorn@rubyforge.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/unicorn.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).