I would use distributed cache and write my own cache controller. Jboss cache
works well for me.
On Fri, Jul 31, 2009 at 9:21 AM, sirmak wrote:
>
> but the code needed for tasks like the cache invalidation on data change in
> a
> concurrent distributed environment is is not seem easy,...
>
> chee
but the code needed for tasks like the cache invalidation on data change in a
concurrent distributed environment is is not seem easy,...
cheers,
Nail Uenlue wrote:
>
> Hello,
>
> As you can code your own cache controller it shouldnt be a hard task to
> archieve this as you can retrieve thos
Hello,
As you can code your own cache controller it shouldnt be a hard task to
archieve this as you can retrieve those instances by your given set of
custer members.
cheers,
Nail
On Fri, Jul 31, 2009 at 4:53 PM, sirmak wrote:
>
> Hi,
>
> I'm investigating tech. possibilities for a new high traff
Hi,
I'm investigating tech. possibilities for a new high traffic web site
project. I want to use ibatis (as myspace, alibaba) but the problem with
ibatis is the lack of distributed or replicated caching of entities with
infinispan. There will be an infinispan hibernate 2nd level cache in the
near
I dont know how you designed your Service layer but putting the
business logic into
some struts classes doesnt seem right to me ;-)
You should follow the POJO way...meaning that you should have a _real_
service layer
which could look like:
MyService.java
public class My
