Re: [eclipselink-users] J2SE Caching Strategy?

["Tim Hollosy" <hollosyt@xxxxxxxxx>]

Shaun,  we are in a client server situation:

~50 RCP apps hitting the same database independently ,so  they would
all technically be "third parties" changing the database behind the
scene, since each client is it's own seperate machine and doesn't
share an L2 cache. So really we need to hit the database 99% of the
time, the 1% of the time we want to hit the cache would be things like
a  list of states pulled from the database to populate a drop down
list. There's no need to hit that every time, but all the other data
is quite volatile.


I think I confused you by talking about multiple EM's, really it
doesn't matter, since the root of the problem is every client is
independent and doesn't share a cache, which would be a common problem
in most J2SE desktop apps.

Hopefull that clears it up :)

Thanks,
Tim




On Mon, May 12, 2008 at 1:40 PM, Shaun Smith <shaun.smith@xxxxxxxxxx> wrote:
>
>  Hi Tim,
>
>     Can you clarify your issues/goals before we get into how best to solve
> them?
>
>  So you don't want the EM-2 to see changes committed by EM-1?  Reading from
> the database will just get you the same answer as you'll get from the L2
>  cache unless you have third parties modifying the database behind the
> scenes.  Is this the root problem you're trying to combat?
>
>      Shaun
>

-- 
./tch