Fausto Lelli wrote: > oookk, so the important thing is that the object is fetched by > the request runtime, and not with/by any other runtime lingering around. > hope I made it this time. :)
Yup yup, you got it. If it didn't matter what runtime an object was associated with, this wouldn't be a problem. One way to solve it would be a thread local runtime, but then we'd be back to square one with Rails, unable to use multiple runtimes across multiple threads. I'm certainly open to suggestions, but by far the easiest solution right now is just to marshal session data into the Java session. Perhaps we could do the marshalling on a per-key basis to cut down on the overhead? Defined session[] to unmarshal from the Java session and session[]= to marshal back in? - Charlie _______________________________________________ Jruby-extras-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/jruby-extras-devel
