Greg, Pat, Most people just use a cron job to clean up old sessions, we usually set it up to run every 15 minutes, how long will you let your sessions live is up to your business needs.
Take a look at: http://railsexpress.de/svn/plugins/sql_session_store/trunk/ And remember that Rails 2 default session store is cookie. I would recommend changing your front end (Apache, Lighttpd, Nginx) configuration to serve directly the stuff under public/ without passing the request to the backend rails processes (mongrels, thins, etc). -- Aníbal Rojas http://hasmanydevelopers.com http://rubycorner.com http://anibal.rojas.com On Apr 29, 5:35 pm, Greg Willits <[EMAIL PROTECTED]> wrote: > Pat Allan wrote: > > My approach with Monit and sessions was to create a specific > > controller & action to poll, and turn sessions off for it. > >http://pastie.textmate.org/188359 > > It does feel like overkill, mind you, and I'm a little surprised that > > calling a static file (which is a more elegant solution) creates a > > session. > > I figured something like that but wasn't sure of the details to pare it > down to the bare essentials. Your code will help. Thanks, I'll see if > that cures it. > > -- gw > > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
