On Jan 29, 2013, at 6:07 PM, Manik Surtani msurt...@redhat.com wrote:
Interesting; looking at the code a bit more, I don't think this offers any
improvements except in the case where expiry is set. Granted, this is a
useful thing to have at that point, but I'm not entirely sure whether it
On Jan 29, 2013, at 6:45 PM, Manik Surtani msurt...@redhat.com wrote:
On 29 Jan 2013, at 17:17, Bela Ban b...@redhat.com wrote:
On 1/29/13 5:25 PM, Sanne Grinovero wrote:
Glad you started work on that :)
Any currentTimeMillis() even today will blow away your cache line and
probably
And in fact the storage-only configuration has also helped uncover a few
topology bugs which were fixed during 5.2.
So that issue will be implicitly be fixed when we release the community
server.
Tristan
On 01/31/2013 10:05 AM, Galder Zamarreño wrote:
I wouldn't bother. I suggested a
Hi,
The REST module is written in Scala (both main + tests). We have some *test*
contributions written in Java (thanks mlinhard).
There was an IRC discussion on whether it's worth migrating the Java
contribution to Scala code or not.
Pros for migrating the contribution from Java to Scala:
-
On 31 Jan 2013, at 11:45, Mircea Markus mmar...@redhat.com wrote:
Hi,
The REST module is written in Scala (both main + tests). We have some *test*
contributions written in Java (thanks mlinhard).
There was an IRC discussion on whether it's worth migrating the Java
contribution to
I've said it before and am repeating myself here: I believe including
Scala code is a very bad decision for the following reasons:
- Not a lot of people are proficient in Scala
- What happens when the people who wrote the Scala code leave ? We'd
have to build up Scala knowledge in house to be
In this special case I'm gonna try to rewrite the test case as an
excercise - it doesn't seem like that much extra work, and I'd rewrite
it anyway
I'm not satisfied with it's current form even if it was to stay in Java.
But this is just postponing of this important question.
As much as I don't
On 31 Jan 2013, at 11:53, Manik Surtani wrote:
On 31 Jan 2013, at 11:45, Mircea Markus mmar...@redhat.com wrote:
Hi,
The REST module is written in Scala (both main + tests). We have some *test*
contributions written in Java (thanks mlinhard).
There was an IRC discussion on whether
On 31 Jan 2013, at 12:28, Michal Linhard wrote:
In this special case I'm gonna try to rewrite the test case as an
excercise - it doesn't seem like that much extra work, and I'd rewrite
it anyway I'm not satisfied with it's current form even if it was to stay in
Java.
-1. If there's a
On 31 Jan 2013, at 12:35, Mircea Markus mmar...@redhat.com wrote:
I don't think that encouraging scala code is good purely for maintenance
reasons. If there's a choice, it should be java. Not saying that learning a
new language is not cool - but in practice people are a bit put off by
On 31 Jan 2013, at 12:37, Manik Surtani wrote:
I don't think that encouraging scala code is good purely for maintenance
reasons. If there's a choice, it should be java. Not saying that learning a
new language is not cool - but in practice people are a bit put off by
maintaining Scala
On 1/31/13 1:37 PM, Manik Surtani wrote:
On 31 Jan 2013, at 12:35, Mircea Markus mmar...@redhat.com
mailto:mmar...@redhat.com wrote:
I don't think that encouraging scala code is good purely for
maintenance reasons. If there's a choice, it should be java. Not
saying that learning a new
On 31 Jan 2013, at 12:08, Bela Ban wrote:
I've said it before and am repeating myself here: I believe including
Scala code is a very bad decision for the following reasons:
- Not a lot of people are proficient in Scala
- What happens when the people who wrote the Scala code leave ? We'd
On 31 Jan 2013, at 12:47, Bela Ban wrote:
On 1/31/13 1:37 PM, Manik Surtani wrote:
On 31 Jan 2013, at 12:35, Mircea Markus mmar...@redhat.com
mailto:mmar...@redhat.com wrote:
I don't think that encouraging scala code is good purely for
maintenance reasons. If there's a choice, it
On 31 Jan 2013, at 12:47, Bela Ban b...@redhat.com wrote:
On 1/31/13 1:37 PM, Manik Surtani wrote:
On 31 Jan 2013, at 12:35, Mircea Markus mmar...@redhat.com
mailto:mmar...@redhat.com wrote:
I don't think that encouraging scala code is good purely for
maintenance reasons. If there's
On 31 Jan 2013, at 13:14, Bela Ban b...@redhat.com wrote:
On 1/31/13 1:48 PM, Mircea Markus wrote:
Agreed on all points.
OTOH learning/using a new language can be good fun, so with that in
mind having Scala in ISPN might be a positive think. From what I saw
discussing with people is
On 31 Jan 2013, at 13:14, Bela Ban b...@redhat.com wrote:
*If* someone wants to learn a new *great* language, learn Clojure. Blows
Scala right out of the water**1 :-)
Also let's not forget:
The most important thing in the programming language is the name. A language
will not succeed
On 31 Jan 2013, at 13:14, Manik Surtani wrote:
On 31 Jan 2013, at 12:47, Bela Ban b...@redhat.com wrote:
On 1/31/13 1:37 PM, Manik Surtani wrote:
On 31 Jan 2013, at 12:35, Mircea Markus mmar...@redhat.com
mailto:mmar...@redhat.com wrote:
I don't think that encouraging scala code is
On 31 Jan 2013, at 13:55, Mircea Markus mmar...@redhat.com wrote:
*Also as a java developer you have the general option of not learning Scala,
but you don't really have the option of not keeping up with Java8.
So you generally only learn new things when you have no other option? ;)
I'm
The release date for Java 8 is not the date when Infinispan will
baseline to Java 8, there's always a lag. In the case of JGroups, some
folks are still on JDK 1.5, would you believe it, and were quite pissed
when I baselined JGroups to JDK 6
On 1/31/13 2:14 PM, Manik Surtani wrote:
On 31
On 31 Jan 2013, at 14:12, Manik Surtani wrote:
On 31 Jan 2013, at 13:55, Mircea Markus mmar...@redhat.com wrote:
*Also as a java developer you have the general option of not learning Scala,
but you don't really have the option of not keeping up with Java8.
So you generally only learn
On 1/31/13 2:17 PM, Manik Surtani wrote:
On 31 Jan 2013, at 13:14, Bela Ban b...@redhat.com wrote:
On 1/31/13 1:48 PM, Mircea Markus wrote:
Agreed on all points.
OTOH learning/using a new language can be good fun, so with that in
mind having Scala in ISPN might be a positive think. From
Hi guys
I hated the fact that I didn't have branch name completions for
remove_topic_branch in zsh, so I wrote an auto-completion script for it:
https://github.com/danberindei/scripts/blob/master/zsh/_remove_topic_branch
Just save it to any directory and then add the directory to fpath in your
Hi,
I am pleased to announce the much awaited final release of Infinispan 5.2.0.
Containing more than 100 features and enhancements and 150 bug fixes [1], this
release the sustained effort of engineering, QA and our growing community - a
big thanks to everyone involved!
Highlights:
- The
Congratulations!
Andy
- Original Message -
From: Mircea Markus mmar...@redhat.com
To: infinispan infinispan-dev@lists.jboss.org
Sent: Thursday, January 31, 2013 1:51:05 PM
Subject: Infinispan 5.2.0.Final is out!
Hi,
I am pleased to announce the much awaited final release of
Congratulations!
Paolo
On 1/31/13 8:51 PM, Mircea Markus wrote:
Hi,
I am pleased to announce the much awaited final release of Infinispan
5.2.0. Containing more than 100 features and enhancements and 150 bug
fixes [1], this release the sustained effort of engineering, QA and
our
On Thu, Jan 31, 2013 at 2:42 PM, Mircea Markus mmar...@redhat.com wrote:
On 31 Jan 2013, at 12:37, Manik Surtani wrote:
I don't think that encouraging scala code is good purely for maintenance
reasons. If there's a choice, it should be java. Not saying that learning a
new language is not
Top work guys. Congrats!
Navin Surtani
Software Engineer
JBoss SET
JBoss EAP
Twitter: @navssurtani
Blog: navssurtani.blogspot.com
- Original Message -
From: Mircea Markus mmar...@redhat.com
To: infinispan infinispan-dev@lists.jboss.org
Sent:
28 matches
Mail list logo
