Comments on: Application error (Rails) http://blogs.herod.net/steven/archives/129 is this thing on? Tue, 06 Jan 2009 15:03:35 +0000 http://wordpress.org/?v=2.6.2 By: Jeremy Voorhis http://blogs.herod.net/steven/archives/129#comment-183 Jeremy Voorhis Sat, 15 Apr 2006 08:19:08 +0000 http://blogs.herod.net/steven/archives/129#comment-183 I have a difficult time attributing this to the stability or instability of Rails. Quite often this is a user error caused by developers running on shared hosts who neglect to lock their Rails application to a particular version. When the Heinous Upgrade occurs, their app might not be ready. Lock your application. That being said, there are certain caveats within Rails that are difficult to address. One of them is the framework's reliance on PStore to persist session data, especially when PStore stores these session files in /tmp. Although this isn't a hard and fast rule, PLANET ARGON prefers to use the ActiveRecord session store to persist session data in session-intensive applications. It takes roughly 5 minutes to implement this. Finally, some of these errors will share the same cause as the class ASP or PHP errors - there is a genuine bug in the application code, a configuration error or a missing dependency. It truly is frustrating for users to encounter these errors - especially if the user also happens to be a Rails developer - but simply attributing this to the framework seems to be a cop-out without bringing any hard evidence to the table. I have a difficult time attributing this to the stability or instability of Rails. Quite often this is a user error caused by developers running on shared hosts who neglect to lock their Rails application to a particular version. When the Heinous Upgrade occurs, their app might not be ready. Lock your application.

That being said, there are certain caveats within Rails that are difficult to address. One of them is the framework’s reliance on PStore to persist session data, especially when PStore stores these session files in /tmp. Although this isn’t a hard and fast rule, PLANET ARGON prefers to use the ActiveRecord session store to persist session data in session-intensive applications. It takes roughly 5 minutes to implement this.

Finally, some of these errors will share the same cause as the class ASP or PHP errors - there is a genuine bug in the application code, a configuration error or a missing dependency.

It truly is frustrating for users to encounter these errors - especially if the user also happens to be a Rails developer - but simply attributing this to the framework seems to be a cop-out without bringing any hard evidence to the table.

]]>