Hi, a stupid question. I've always taken for granted that the "ruby session" was difficult to marshall because it is bound to the runtime. Am I missing something here ? :)
Fausto. On 4/17/07, Ola Bini <[EMAIL PROTECTED]> 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? > > Cheers > > -- > Ola Bini (http://ola-bini.blogspot.com) > JvYAML, RbYAML, JRuby and Jatha contributor > System Developer, Karolinska Institutet (http://www.ki.se) > OLogix Consulting (http://www.ologix.com) > > "Yields falsehood when quined" yields falsehood when quined. > > > _______________________________________________ > Jruby-extras-devel mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/jruby-extras-devel > _______________________________________________ Jruby-extras-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/jruby-extras-devel
