On 18/04/2007, at 3:51 AM, Ola Bini wrote: > Ashish Sahni wrote: >> #2 seems to be a much better way for various reasons - clustering >> support, session survival across processes etc. >> I suppose that the changes needed for this would be in the >> rails-integration layer (as opposed to the jruby layer). Is that >> right ? >> >> > Yeah, and I've already committed a first fix for this; the major > change > is that instead of placing each session attribute in a separate Java > session attribute, this version will just Marshal the Ruby session > into > one attribute on the Java session. > > You RI guys, can you tell me if this looks dead wrong for some reason?
Awesome! This seems to solve the problems I was having! Our app is actually now relatively stable in JRuby. It is certainly the correct semantics for the session wrt Rails compatability. In Rails your session will always be serialized after each request. Cheers, Jon ---- New from ThoughtWorks: Mingle, an Agile project management application. Mingle. Project Intelligence. Powerfully Simple. More at http://studios.thoughtworks.com _______________________________________________ Jruby-extras-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/jruby-extras-devel
