Re: [infinispan-dev] JCache implementation documentation

2013-05-02 Thread cotton-ben
/> QUESTION: Is there a native-Infinispan config to indicate an OPTIMISTIC > policy (btw, this is not yet provided for via JSR-107 API) ? I.e. does > Infinispan allow an OPTIMISTIC READ_COMMITTED isolation config that would > result in the capability for TX_THR_2 to physically read the un-commit

Re: [infinispan-dev] JCache implementation documentation

2013-05-02 Thread Galder Zamarreño
On May 1, 2013, at 11:24 AM, cotton-ben wrote: >> Failure to block that @t=2 >> access to the un-committed CREDIT has dire-consequences ... e.g. if >> TX_THR_1 >> executes rollback() on the credit @t=1 ! OUCH. If Infinispan does not >> block TX_THR_2 read @t=2 then it proceeds as if the cr

Re: [infinispan-dev] JCache implementation documentation

2013-05-01 Thread cotton-ben
> Failure to block that @t=2 > access to the un-committed CREDIT has dire-consequences ... e.g. if > TX_THR_1 > executes rollback() on the credit @t=1 ! OUCH. If Infinispan does not > block TX_THR_2 read @t=2 then it proceeds as if the credit happened! /^ No, if it doesn't block, it reads

Re: [infinispan-dev] JCache implementation documentation

2013-05-01 Thread Galder Zamarreño
On Apr 29, 2013, at 1:28 PM, cotton-ben wrote: >> >> Please consider taking a look at the attached plan for Test #1. >> >> It is very simple. A "Savings Account" is cached in Infinispan 5.3.0.A. >> Two transactional threads simultaneously operate (access/mutate) on the >> "Savings Accoun

Re: [infinispan-dev] JCache implementation documentation

2013-05-01 Thread Galder Zamarreño
On Apr 29, 2013, at 1:03 PM, cotton-ben wrote: > > /> implementation). Will you extend this test to also audition the usage of >> javax.transaction.UserTransaction (arjuna, et. al. implementations?) and >> its >> JCACHE factory bridge via javax.cache.CacheManager.getUserTransaction() ? > > ^

Re: [infinispan-dev] JCache implementation documentation

2013-04-29 Thread cotton-ben
> > Please consider taking a look at the attached plan for Test #1. > > It is very simple. A "Savings Account" is cached in Infinispan 5.3.0.A. > Two transactional threads simultaneously operate (access/mutate) on the > "Savings Account". Transactional Thread #2 indicates via the JSR-107 A

Re: [infinispan-dev] JCache implementation documentation

2013-04-29 Thread cotton-ben
/> implementation). Will you extend this test to also audition the usage of > javax.transaction.UserTransaction (arjuna, et. al. implementations?) and > its > JCACHE factory bridge via javax.cache.CacheManager.getUserTransaction() ? ^ H, which test are you refering to exactly? / *See line

Re: [infinispan-dev] JCache implementation documentation

2013-04-29 Thread Galder Zamarreño
On Apr 28, 2013, at 7:08 PM, cotton-ben wrote: > Hi Galder, > > Thanks for your off-line email exchange confirming that community > contributed tests of 5.3.0A's JSR-107 transactions option capability (and > compliance) are welcome. > > Here is what we would like to contribute initially. > >

Re: [infinispan-dev] JCache implementation documentation

2013-04-29 Thread Galder Zamarreño
On Apr 25, 2013, at 1:06 PM, Mircea Markus wrote: > Very nice writeup Galder! And nice crash-course to JCache API: it seems very > well designed for distributed system, the put and putAndGet methods in > particular. > > Some notes: > Dependencies > - would be nice to write how this can be us

Re: [infinispan-dev] JCache implementation documentation

2013-04-29 Thread Galder Zamarreño
On Apr 23, 2013, at 6:03 PM, cotton-ben wrote: > > Very nice work Galder. > > Couple of questions re: Infinispan 5.3.0 ambitions/capabilities to provide > JSR-107 transactions option. > > 1. We noticed on your GitHub branch that you have JCACHE Transactions test > code. The code uses java

Re: [infinispan-dev] JCache implementation documentation

2013-04-28 Thread cotton-ben
PPT for TEST #1. policy=PESSIMISTIC Infinispan-5.3.0.A1=JSR-107_TRANSACTIONS_OPTION=DIRTY_READ_INTOLERANCE_TEST.docx.pptx -- View

Re: [infinispan-dev] JCache implementation documentation

2013-04-28 Thread cotton-ben
Hi Galder, Thanks for your off-line email exchange confirming that community contributed tests of 5.3.0A's JSR-107 transactions option capability (and compliance) are welcome. Here is what we would like to contribute initially. 1. A test that 5.3.0.A can (both optimistically and pessimistically

Re: [infinispan-dev] JCache implementation documentation

2013-04-25 Thread Mircea Markus
Very nice writeup Galder! And nice crash-course to JCache API: it seems very well designed for distributed system, the put and putAndGet methods in particular. Some notes: Dependencies - would be nice to write how this can be used without maven as well. Based on the # of distribution downloads

Re: [infinispan-dev] JCache implementation documentation

2013-04-23 Thread cotton-ben
Very nice work Galder. Couple of questions re: Infinispan 5.3.0 ambitions/capabilities to provide JSR-107 transactions option. 1. We noticed on your GitHub branch that you have JCACHE Transactions test code. The code uses javax.transaction.TransactionManager (ajuna implementation). Will you