I am not sure I totally grasp what you mean by:
Worth noting I think that adding auto-locking on classes of instances that aren't ever shared has no impact. Distributed locks only occur when a shared object is locked on. So the number of locks one generally needs is usually small. Would it be possible to get some elaboration or see a brief example? Maybe I am just being dumb because of the long day....:) ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven Harris Sent: Thursday, December 06, 2007 8:33 PM To: [email protected] Cc: [EMAIL PROTECTED] Subject: Re: [tc-users] [tc-dev] global lock level Worth noting I think that adding auto-locking on classes of instances that aren't ever shared has no impact. Distributed locks only occur when a shared object is locked on. So the number of locks one generally needs is usually small. Can you give a little more detail and which parts you think need concurrent locks? Cheers, Steve On Dec 6, 2007, at 8:29 PM, Jason Chaffee wrote: I should add that we want concurrent on about 98% of our code and locks on about 2%. It would really suck to configure this if you can't set a global default. Using wildcards would not be a good solution either based on our code. ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Chaffee Sent: Thursday, December 06, 2007 5:06 PM To: [email protected]; [EMAIL PROTECTED] Subject: Re: [tc-users] [tc-dev] global lock level Performance is not a concern and neither is the data being deterministic because for the most part there is only person making changes and we need these changes to propagate to many nodes instead of configuring each machine. I can honestly say this is big issue against Terracotta because it appears JBossPOJOCache will support this. ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Taylor Gautier Sent: Thursday, December 06, 2007 4:13 PM To: [EMAIL PROTECTED] Cc: [email protected] Subject: Re: [tc-dev] [tc-users] global lock level To answer your question, no, there is not a way to set the default lock level. I feel compelled to point out except for very specific uses, concurrent is not really a good idea. Why are you thinking to go with concurrent? If you want better performance you should use a combination of read and write locks. Jason Chaffee wrote: Is it possible to set a global default lock level? By default, it is currently set to 'write' I would like to set it to 'concurrent' and lock the methods that need it. Jason Chaffee Software Architect/Server Team Manager <image001.jpg> <http://www.tvworks.com> APPLICATIONS DIVISION [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Tel : 415.380.6316 Cell: 415.637.8061 ________________________________ _______________________________________________ tc-users mailing list [EMAIL PROTECTED] http://lists.terracotta.org/mailman/listinfo/tc-users _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
_______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
