>> But it is do-able, although not easy, I don't think you can get away >> with just trying to access the session array itself in a thread that's >> out of the request loop.
Sorry, this is a topic of interest to me that noone else is ever interested in talking about. PPS: REALLY, if you decide you want to set off a thread that will persist after the response is returned, despite the general pain in the neck of doing that cause neither ActiveRecord nor MRI 1.8 Ruby are entirely happy with it (but it's still possible if you take the right precautions)... AND... you need that thread to store state that later requests can access.... Consider just storing it in the db as an ActiveRecord rather than trying to put it in a session. All in all easier to deal with, at least if your thread already was using ActiveRecord anyway (which supplies it's own headaches). Worth considering, it's a trade-off as to what sort of headaches you want to deal with. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
