You could chain multiple TcpDelegatingCacheLoaders...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4065305#4065305
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4065305
___
Sorry if i wasn't more clear.
I have these components distributed geografically: management, provider,
reseller and each one has its own cache: management-cache, provider-cache,
reseller-cache and I have the core of the application separately with its own
cache too (core-cache). The core-cache
The linked thread pertains to cache loaders. There can be only one cache loader
per thread.
What's confusing to me (and probably to others) is why do you need to segregate
the data into separate cache instances, and what is the point of copying all
the caches' data into one core cache?
If you
You could use invalidation so only eviction messages are broadcast, but this
means that the caches need to be in the same cluster.
Just because they are in different LANs doesn't mean they cannot be clustered -
consider using TCP or TCP_NIO, or even the TUNNEL protocol in your cluster
