[jbosscache-dev] Method storeEntireState is ambiguous with null parameter

[Vladimir Blagojevic]

Yeah I agree with your concerns. I am not a performance expert but as I
see it our 
performance improvement boundary ends when we reach the contents of 
cache (value object in NodeData attrs map). Unless we force customers 
to implement some special interfaces there is not much more we can do?

So in summary we move forward with Cacheloader API that has only 4
load/store methods:

void loadEntireState(ObjectOutputStream os) throws Exception;
void storeEntireState(ObjectInputStream is) throws Exception;
void loadState(Fqn subtree,ObjectOutputStream os) throws Exception;
void storeState(Fqn subtree,ObjectInputStream is) throws Exception;

Please hold of any work on all cacheloaders until the end of the week if
possible.


> -----Original Message-----
> From: Bela Ban 
> Sent: Tuesday, August 29, 2006 12:26 PM
> To: Vladimir Blagojevic
> Cc: Manik Surtani; jbosscache-dev at lists.jboss.org
> Subject: Re: [jbosscache-dev] Method storeEntireState is 
> ambiguous with null parameter
> 
> I understand your reasoning, but what I'm asking is "is the 
> NodeData marshalling mechanism efficient ?". Or - since there 
> are not yet too many CacheLoader implementations *which 
> interact with each other* - should we come up with a 
> (potentially) more efficient marshalling format ? See, I 
> wrote that format down some time ago, and wasn't too 
> concerned about efficiency.
>