Thursday, December 26, 2002, 10:34:54 PM, you wrote: DH> Using the Version Strategy as an example, if you have one app DH> server talking to one database (equiv to commit-option B), will DH> this make mostly-read transactions better or not make that much of a DH> difference?
Actually, this is what the optimistic locking is for. Specifying it, you let different transactions to deal with the same entity instead of just one tx at a time. DH> Actually, now that I'm thinking about it, would someone help DH> enlighten my dim LED with a simple layout about when this cool DH> Optimistic-Locking would offer the best results, and when it is not (I DH> assume highly-volatile Tx entities would not, but assuming equals ass-u-me)? DH> Single JBoss, Commit-Option A, D DH> --Read only entities, mostly-read entities, and highly-volatile entities DH> Single JBoss, Commit-Option B DH> --Read only entities, mostly-read entities, and highly-volatile entities DH> Multi-Jboss Cluster, Commit-Option C DH> --Read only entities, mostly-read entities, and highly-volatile entities I am not sure I can give a general answer on the best practices. I can ensure it works with each commit option. Other things, I think, depend on the project specifics. alex DH> Gone through Dain's great JbossCMP pay-for docs, well worth it! ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
