I think it's a good idea. Amongst other things, it'd allow for a settings.xml
file to be provided without littering the pom.xml files.
Navin, have you written one already?
Cheers,
On Jun 14, 2013, at 4:04 AM, Navin Surtani nsurt...@redhat.com wrote:
Greetings all,
I had this idea
Hi guys,
I've been looking at TxDistributionInterceptor and I have a couple of
questions (assuming REPEATABLE_READ isolation level):
#1. why are we doing a remote get each time we write on a key? (huge
perform impact if the key was previously read)
#2. why are we doing a dataContainer.get()
On 17 Jun 2013, at 11:52, Pedro Ruivo pe...@infinispan.org wrote:
I've been looking at TxDistributionInterceptor and I have a couple of
questions (assuming REPEATABLE_READ isolation level):
#1. why are we doing a remote get each time we write on a key? (huge
perform impact if the key was
On 06/17/2013 12:56 PM, Mircea Markus wrote:
On 17 Jun 2013, at 11:52, Pedro Ruivo pe...@infinispan.org wrote:
I've been looking at TxDistributionInterceptor and I have a couple of
questions (assuming REPEATABLE_READ isolation level):
#1. why are we doing a remote get each time we write
On 17 Jun 2013, at 13:58, Pedro Ruivo pe...@infinispan.org wrote:
After this analysis, it is possible to break the isolation between
transaction if I do a get on the key that does not exist:
tm.begin()
cache.get(k) //returns null
//in the meanwhile a transaction writes on k and commits
On Mon, Jun 17, 2013 at 3:58 PM, Pedro Ruivo pe...@infinispan.org wrote:
On 06/17/2013 12:56 PM, Mircea Markus wrote:
On 17 Jun 2013, at 11:52, Pedro Ruivo pe...@infinispan.org wrote:
I've been looking at TxDistributionInterceptor and I have a couple of
questions (assuming
On Mon, Jun 17, 2013 at 11:11 AM, Dan Berindei dan.berin...@gmail.comwrote:
On Mon, Jun 17, 2013 at 3:58 PM, Pedro Ruivo pe...@infinispan.org wrote:
On 06/17/2013 12:56 PM, Mircea Markus wrote:
On 17 Jun 2013, at 11:52, Pedro Ruivo pe...@infinispan.org wrote:
I've been looking at
On 17 Jun 2013, at 16:11, Dan Berindei dan.berin...@gmail.com wrote:
I think that, given that the local node is not owner, the lock acquisition
is redundant even for pessimistic caches.
Mind creating a test to check if dropping that lock acquisition doesn't
break things?
I created a
@Matej, are you still having issues with this?
I've created a test and I'm unable to get this to fail any more...
Cheers,
On Oct 3, 2012, at 10:25 PM, Mircea Markus mircea.mar...@jboss.com wrote:
Thanks for raising this Vladimir, I've commented on the JIRA.
On 1 Oct 2012, at 10:19,
More about it here:
http://infinispan.blogspot.de/2013/06/infinispan-530cr2-is-out.html
Cheers,
--
Mircea Markus
Infinispan lead (www.infinispan.org)
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
Hi,
Master was updated to point to 6.0.0. Please port any pending 5.3.x fixes to
both master and the 5.3.x branch.
Cheers,
--
Mircea Markus
Infinispan lead (www.infinispan.org)
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
Hi,
Following the tradition, each Infinispan release is code is a beer.
Suggestions?
I'll start:
- Infinium
Cheers,
--
Mircea Markus
Infinispan lead (www.infinispan.org)
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
Hi Navin,
The master now pointing to 6.0.0 so whenever you have the time for test
migration you can go ahead
Tristan is also working on repackaging, but starting with the following should
avoid the two of you overlapping.
After that please ping Tristan on what can be done next.
And again -
Human Fish
* https://www.facebook.com/HumanFishBrewery
On Jun 17, 2013, at 10:37 PM, Mircea Markus mmar...@redhat.com wrote:
Hi,
Following the tradition, each Infinispan release is code is a beer.
Suggestions?
I'll start:
- Infinium
Cheers,
--
Mircea Markus
Infinispan lead
Seriously Bad Elf (or have ya'll already used that?)
http://beeradvocate.com/beer/profile/7944/26887
--
View this message in context:
http://infinispan-developer-list.980875.n3.nabble.com/infinispan-dev-release-name-for-Infinispan-6-0-0-tp4027428p4027431.html
Sent from the Infinispan
15 matches
Mail list logo