Ashish Sahni wrote: > I don't quite follow the active/passive explanation. If #2 ie, > active-marshalling is good enough to reproduce state on the other side, > why do we need 'reattachment to runtimes' in #1 to save/reproduce state. > To rephrase my explanation of #1, can't > the JRuby root object implement java.io.Externalizable so that > implementation of the interface is jruby-marshalling ?
Because we have no way to access a JRuby runtime when it's deserialized on the other side. How do you unmarshal Ruby content if you can't get a reference to the Marshal class? The difference in #2 is that a Ruby call initiates the marshaling and another Ruby call initiates the unmarshaling, where in #1, it's a Java call outside JRuby on both ends (i.e. the app server's code for session replication). Have a look at MarshalStream and UnmarshalStream in JRuby. - Charlie _______________________________________________ Jruby-extras-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/jruby-extras-devel
