Why not just store the data in a separate table as a serialized object or CSV in a blob and run a job to clear out old ones? Then you can just store the id of the stored data in the session.
Jarin On Oct 7, 6:56 pm, Scott Olmsted <[email protected]> wrote: > I'm creating an application that displays a table of information > based on user input. It is time-expensive to create the data for the table. > > The user can, after seeing the HTML table, click on a 'Download' link > and receive the data in CSV form. > > I don't want to compute the data again. Is there a way to persist the > data without putting it in the database? It could be too large to fit > in the session, so that's out. > > My first thought, stuff it in a global variable (horrors! - oh, get > real, globals can have their uses), is apparently a bad idea because > a deployment with multiple mongrels or a similar scheme has multiple > code/data spaces that don't communicate. > > Thanks, > > Scott --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
