)? Do you have any
suggestions on how to handle this scenario?
Thanks, Abitha.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871379#3871379
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode
Thank you. I would like to know about some production level deployments.
How many nodes, (with small objects associated) is typically recommended in a
tree cache? Maybe a range would give me a better idea.
Are there any best practices for using TreeCache?
View the original post :
http://
Thank you for the quick response Ben. That helps. My main concerns are in the
area of performance.
>From what I read, if I use the cache loader, then every single node is
>persisted on a backend store. Correct? Will that not be a big dent on
>performance?
What if I dont have/want a cache load
Ok, so now that I have successfully implemented a plain JBossCache within JBoss
3.2.6, I have some basic, performance related questions.
1. In the plain JBossCache, it looks like I need to do a put everytime after an
object is changed. Is that right? For example, if I have a vector assigned as
v
Can I use TreeCacheAOP - thereby replicating only attributes that change, as
opposed to replicating entire objects or sessions across servers - within JBOSS
3.2.6 with POJOs?
Thanks.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870256#3870256
Reply to th
