As Charlie suggested (and I had thought to do before, but was too tired), everything works fine if I change the environment from development to production so that it doesn't do any reloading around each request.
I forgot about the rails CGI:Session::MemoryStore and I actually figured it might serialize anyway. But it doesn't. And it has exactly the same problem. So it's not solely an issue with the servlet session but it's of more interest to "us" than the core rails folks since next to nobody is using the memory store, I expect. >From the pure rails side, is it a bug that MemoryStore may not work with module reloading, e.g., development mode, or a "don't do that"/"won't fix" kind of thing? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
