-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

(2011/11/13 1:58), Mike Perham wrote:
> My use case: I want to use Rails in thread-safe mode in production
> so I don't have to fork 20 Ruby processes to handle 20 concurrent
> requests.  When developing, Rails auto loads classes on every
> request.  This auto loading is critical to Rails' rapid development
> cycle and there's no way I'm going to disable it.  Unfortunately
> the current autoload behavior makes the development environment
> incompatible with thread-safe mode.

I should read ActiveSupport source code first but please allow me to
post lazy question.  Does Rails development mode use autoload?  It is
doing constant lookup by itself I guess, but I could be wrong, of course.

You might be using autoload in your library though...

> Since no developer wants to lose the rapid development cycle and no
> developer is crazy enough to run a very different configuration in
> production than development (going from non-thread-safe to
> thread-safe between dev and prod is a huge change), no one
> currently uses thread-safe mode.

Ah, thank you.  I was not aware of the reason.  Good to know.  I
indeed want to fix that situation.

> I will try trunk in a few days and report back if it solves the
> problem.

Thank you!  I'm looking forward to hear the result.

// NaHi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)

iQEcBAEBAgAGBQJOvx7bAAoJEC7N6P3yLbI2eIQH/i5pmRNaQgLg8X0BlRLybXXx
3n+N6+JS00I8EreblBpkvDLy62YXJTy3V+ahKDZupozC2oALRdjk8QlYSH4H3kTp
9R6ZzyCqjpfiilowF5uXaxP7qeGIGgYxBvWIxZgLGwdyyi8DK1YgwD6VklOwsfab
uLNQinuG8Rpbl7ic4Uu+kHmIh3IGDQFsXzxwzbBlmMi8DT+rf2CLGnBkCQFY8kyC
wcp/4s+K+5GJWtVM4yJNSMZhduwNbMZs8iAy6iOItEAFTabXUULWexUlkL3RhFVu
HYDwjCf7NqPFalLfwkWxZEdZpLZ7YifVFNW93XvyaKFuxAzgEFvW8vQ4UJbtVz4=
=bzOU
-----END PGP SIGNATURE-----