This project is archived and is in readonly mode.
Drop object reloading and use forking instead
Reported by Scott Taylor | June 23rd, 2009 @ 02:44 PM | in 3.x
It would be great to drop all of the complicated crazy object reloading, and move to something like shotgun which can fork on every request.
Comments and changes to this ticket
-
Scott Taylor June 23rd, 2009 @ 02:44 PM
- Tag changed from “reloading, shotgun, sinatra” to “feature_request, reloading, shotgun, sinatra”
-
Scott Taylor June 23rd, 2009 @ 02:44 PM
- no changes were found...
-
CancelProfileIsBroken June 23rd, 2009 @ 03:13 PM
- State changed from “new” to “incomplete”
This falls under the heading of "Creating a feature request - please don't" (see sidebar to right).
I'm sure core would be happy to look at a patch that implemented a forking strategy for Rails, but just suggesting a major bit of reachitecting isn't really appropriate for the issue tracker.
You could also post to rails-core to judge whether anyone else is enthusiastic enough to want to work on this with you.
-
-
-
Rohit Arondekar October 9th, 2010 @ 04:04 AM
- State changed from “incomplete” to “stale”
- Importance changed from “” to “”
Marking ticket as stale. If this is still an issue please leave a comment with suggested changes, creating a patch with tests, rebasing an existing patch or just confirming the issue on a latest release or master/branches.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
CancelProfileIsBroken
Jeremy Kemper
Rohit Arondekar
Scott Taylor