Ruby on Rails 4.0.0.beta1 released
weblog.rubyonrails.org
Ruby on Rails 4.0.0.beta1 released
1–10 of 91 posts
Re: Ruby on Rails 4.0.0.beta1 released
#2does threadsafe and ruby 2.0 mean we can create multiple instances with something like unicorn without forking the entire codebase?
Re: Ruby on Rails 4.0.0.beta1 released
#3Hello everyone! I am MEGA EXCITED for this release, as it's the first version in which I'm a committer. Wooo! In addition, 954 other intrepid Rubyists in total contributed to this release: http://contributors.rubyonrails.org/edge/contributors
Please note that this is a beta, not an rc, so some things may be a bit wonky. Please file an issue on GitHub and I will do everything I can to help you help us iron out all the kinks.
❤❤❤
(Also, I am on a plane and my battery is almost dead, so I may drop out of this thread soon. Ill read it when I'm home.)
Re: Ruby on Rails 4.0.0.beta1 released
#4does threadsafe and ruby 2.0 mean we can create multiple instances with something like unicorn without forking the entire codebase?
Funny thing about unicorn is, forking is core to its design. It may handle threading now, but when I last looked at its code fork() and traditional IPC via signals were core to its operation. Puma looks like the more thread-oriented choice these days.
Re: Ruby on Rails 4.0.0.beta1 released
#5does threadsafe and ruby 2.0 mean we can create multiple instances with something like unicorn without forking the entire codebase?
Ruby 2.0 still has the GIL so if you want to run a threaded web server you'll still need to be using rubinius or jruby.
Re: Ruby on Rails 4.0.0.beta1 released
#6does threadsafe and ruby 2.0 mean we can create multiple instances with something like unicorn without forking the entire codebase?
Funny thing about unicorn is, forking is core to its design. It may handle threading now, but when I last looked at its code fork() and traditional IPC via signals were core to its operation. Puma looks like the more thread-oriented choice these days.
Last I looked Puma and jruby were the go-to options for threaded stuff.
Re: Ruby on Rails 4.0.0.beta1 released
#7Hello everyone! I am MEGA EXCITED for this release, as it's the first version in which I'm a committer. Wooo! In addition, 954 other intrepid Rubyists in total contributed to this release: http://contributors.rubyonrails.org/edge/contributors Please note that this is a beta, not an rc, so some things may be a bit wonky. Please file an issue on GitHub and I will do everything I can to help you help us iron out all the…
I'm curious to know if these examples of potential SQL injection tested against 3.2.11 have been dealt with in 4.0? Would be great to see these possible problems tidied up.
Re: Ruby on Rails 4.0.0.beta1 released
#8Hello everyone! I am MEGA EXCITED for this release, as it's the first version in which I'm a committer. Wooo! In addition, 954 other intrepid Rubyists in total contributed to this release: http://contributors.rubyonrails.org/edge/contributors Please note that this is a beta, not an rc, so some things may be a bit wonky. Please file an issue on GitHub and I will do everything I can to help you help us iron out all the…
I'm curious to know if these examples of potential SQL injection tested against 3.2.11 have been dealt with in 4.0? Would be great to see these possible problems tidied up. http://rails-sqli.org/
I am not a member of the security team, but it's my understanding that all security patches were also applied against master where appropriate.
(The security team is a subset of the core team, in accordance with least privilege and all that.)
Re: Ruby on Rails 4.0.0.beta1 released
#9Hello everyone! I am MEGA EXCITED for this release, as it's the first version in which I'm a committer. Wooo! In addition, 954 other intrepid Rubyists in total contributed to this release: http://contributors.rubyonrails.org/edge/contributors Please note that this is a beta, not an rc, so some things may be a bit wonky. Please file an issue on GitHub and I will do everything I can to help you help us iron out all the…
Proud to be on the contributor list for this one - any of you considering contributing, it's not hard at all, the team makes it really easy.
Re: Ruby on Rails 4.0.0.beta1 released
#10does threadsafe and ruby 2.0 mean we can create multiple instances with something like unicorn without forking the entire codebase?
I'm not sure what you mean by 'forking the entire codebase'.
Even if Rails3, though, Rails supported multi-threaded request dispatching IF you had an app server stack that supported it.
In Rails3, you just had to explicitly turn it on with `config.threadsafe!`. Rails4 makes that the default, always on. That's really the only difference. There are at least a few concurrency-related bugs that have been fixed in Rails4 (I'm actually not sure how many), but even Rails3 was officially documented to do multi-threaded concurrent request dispatch just fine. (Actually even Rails 2.2 was!)
Finding a mature, reliable, well-documented app server stack that supports multi-threaded concurrent request dispatch may be harder. I can not say which do and which don't, but there are at least some potential options (including puma, which, if I understand it right, has multi-threaded concurrent request handling as part of it's original core use case).
I AM hoping that Rails4's "multi-threaded request dispatch on by default" situation will make the community pay more attention to this use case, result in more app servers supporting it first-class robustly, and any remaining bugs around concurrency being found and fixed. While Rails3 was documented to support this anyway (since Rails 2.2!), it has been mostly ignored by the community, for some reason.
(Sadly, while Passenger Enterprise 4 will support multi-threaded concurrent request dispatch, the Passenger folks are intentionally reserving this feature for Enterprise, the free one won't)