[infinispan-dev] distributed execution - invoking commands on self

[Manik Surtani]

I still think Mircea's suggestion is very valid.  Try cloning first.  If cloning is not supported then serialize/deserialize.  And in any case you only need 1 copy of the callable to send across to all other nodes, and the original copy for local execution, right?


On 18 Apr 2011, at 11:24, Galder Zamarreño wrote:

> 
> On Apr 15, 2011, at 3:23 PM, Vladimir Blagojevic wrote:
> 
>> On 11-04-15 4:34 AM, Galder Zamarreño wrote:
>>> On Apr 12, 2011, at 7:45 PM, Vladimir Blagojevic wrote:
>>> 
>>>> Yeah, it would be too strict to require Callable to be Cloneable so I
>>>> would opt out to serialization/deserialization as a clone method.
>>>> 
>>>> Galder, do out have a recommended mechanism for this in your marshalers?
>>> Not really. I think you should marshall or clone it before executing operations against it.
>>> 
>>> For marshalling data, you just have to see what is done in the lazy deserialization code, just get hold of the VersionAwareMarshaller and marshall it.
>> How do I get a hold of it? I found Marshaller registered in 
>> GlobalComponentRegistry but I could not find API to access it. I used a 
>> regular serialization for cloning and it works ok but I'd definitely 
>> prefer to use Marshaller.
> 
> Seems like you figured out eventually :) -  globalRegistry.getComponent(StreamingMarshaller.class)
> 
>> 
>> 
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> 
> --
> Galder Zamarreño
> Sr. Software Engineer
> Infinispan, JBoss Cache
> 
> 
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

--
Manik Surtani
manik at jboss.org
twitter.com/maniksurtani

Lead, Infinispan
http://www.infinispan.org