5:38 a.m.
Yup, it needs to happen sometime. But the question is, when?
Is there anyone out there who desperately needs Infinispan to work on Java 6?
Cheers
Manik
--
Manik Surtani
manik(a)jboss.org
twitter.com/maniksurtani
Platform Architect, JBoss Data Grid
http://red.ht/data-grid
6:06 a.m.
On 5/23/13 12:38 PM, Manik Surtani wrote:
Yup, it needs to happen sometime. But the question is, when?
Is there anyone out there who desperately needs Infinispan to work on Java 6?
I got a lot of pushback when I moved the required JDK in JGroups to 1.5
(people were still using 1.4), and the same for moving from 1.5 to 1.6,
so I anticipate this won't be different for moving to 1.7 as baseline.
I personally would not mind waiting for JGroups 5 to move to JDK 7, as
this gives users a bit more time and I won't require JDK 7 before
JGroups 5 anyway, as the NIO2 stuff won't be in JGroups 4, only in 5.
But if you guys need to move to JDK 7 in Infinispan 6 already, then
that's fine with me, too.
I guess the AS has some requirements, too, so if they decide to move to
JDK 7, then we'll have to make that move too
--
Bela Ban, JGroups lead (http://www.jgroups.org)
6:11 a.m.
WildFly already requires Java7.
Hibernate Search will likely stay a bit longer on 6, and depends on
Infinispan, but this dependency is an isolated module so we can live
with it by making our build a bit more painful. Users would then need
Java7 only if they want to use the Infinispan extensions.
Sanne
On 23 May 2013 12:06, Bela Ban <bban(a)redhat.com> wrote:
On 5/23/13 12:38 PM, Manik Surtani wrote:
> Yup, it needs to happen sometime. But the question is, when?
>
> Is there anyone out there who desperately needs Infinispan to work on Java 6?
I got a lot of pushback when I moved the required JDK in JGroups to 1.5
(people were still using 1.4), and the same for moving from 1.5 to 1.6,
so I anticipate this won't be different for moving to 1.7 as baseline.
I personally would not mind waiting for JGroups 5 to move to JDK 7, as
this gives users a bit more time and I won't require JDK 7 before
JGroups 5 anyway, as the NIO2 stuff won't be in JGroups 4, only in 5.
But if you guys need to move to JDK 7 in Infinispan 6 already, then
that's fine with me, too.
I guess the AS has some requirements, too, so if they decide to move to
JDK 7, then we'll have to make that move too
--
Bela Ban, JGroups lead (http://www.jgroups.org)
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
6:59 a.m.
Just to clarify, Infinispan 6.0 will *not* baseline on Java 7.
My email is just to get a feel of who still requires Java 6. My gut feel is that
we're at least a year away from baselining on Java 7, possibly for Infinispan 8.0 (and
JGroups 5.0).
- M
On 23 May 2013, at 12:11, Sanne Grinovero <sanne(a)infinispan.org> wrote:
WildFly already requires Java7.
Hibernate Search will likely stay a bit longer on 6, and depends on
Infinispan, but this dependency is an isolated module so we can live
with it by making our build a bit more painful. Users would then need
Java7 only if they want to use the Infinispan extensions.
Sanne
On 23 May 2013 12:06, Bela Ban <bban(a)redhat.com> wrote:
>
>
> On 5/23/13 12:38 PM, Manik Surtani wrote:
>> Yup, it needs to happen sometime. But the question is, when?
>>
>> Is there anyone out there who desperately needs Infinispan to work on Java 6?
>
> I got a lot of pushback when I moved the required JDK in JGroups to 1.5
> (people were still using 1.4), and the same for moving from 1.5 to 1.6,
> so I anticipate this won't be different for moving to 1.7 as baseline.
>
> I personally would not mind waiting for JGroups 5 to move to JDK 7, as
> this gives users a bit more time and I won't require JDK 7 before
> JGroups 5 anyway, as the NIO2 stuff won't be in JGroups 4, only in 5.
>
> But if you guys need to move to JDK 7 in Infinispan 6 already, then
> that's fine with me, too.
>
> I guess the AS has some requirements, too, so if they decide to move to
> JDK 7, then we'll have to make that move too
>
> --
> Bela Ban, JGroups lead (http://www.jgroups.org)
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
twitter.com/maniksurtani
Platform Architect, JBoss Data Grid
http://red.ht/data-grid
7 a.m.
On 5/23/13 1:11 PM, Sanne Grinovero wrote:
WildFly already requires Java7.
OK. This doesn't mean though that JGroups 4 has to require JDK 7; it can
still baseline on JDK 6. As long as
jgroups version <= infinispan version <= wildfly version
, we're fine. Of course, we can always link to a module requiring a
higher JDK than the component consuming us *dynamically*
Hibernate Search will likely stay a bit longer on 6, and depends on
Infinispan, but this dependency is an isolated module so we can live
with it by making our build a bit more painful. Users would then need
Java7 only if they want to use the Infinispan extensions.
Sanne
On 23 May 2013 12:06, Bela Ban <bban(a)redhat.com> wrote:
>
>
> On 5/23/13 12:38 PM, Manik Surtani wrote:
>> Yup, it needs to happen sometime. But the question is, when?
>>
>> Is there anyone out there who desperately needs Infinispan to work on Java 6?
>
> I got a lot of pushback when I moved the required JDK in JGroups to 1.5
> (people were still using 1.4), and the same for moving from 1.5 to 1.6,
> so I anticipate this won't be different for moving to 1.7 as baseline.
>
> I personally would not mind waiting for JGroups 5 to move to JDK 7, as
> this gives users a bit more time and I won't require JDK 7 before
> JGroups 5 anyway, as the NIO2 stuff won't be in JGroups 4, only in 5.
>
> But if you guys need to move to JDK 7 in Infinispan 6 already, then
> that's fine with me, too.
>
> I guess the AS has some requirements, too, so if they decide to move to
> JDK 7, then we'll have to make that move too
--
Bela Ban, JGroups lead (http://www.jgroups.org)
6:01 p.m.
Sent from my iPhone
On 23 May 2013, at 12:06, Bela Ban <bban(a)redhat.com> wrote:
On 5/23/13 12:38 PM, Manik Surtani wrote:
> Yup, it needs to happen sometime. But the question is, when?
>
> Is there anyone out there who desperately needs Infinispan to work on Java 6?
I got a lot of pushback when I moved the required JDK in JGroups to 1.5
(people were still using 1.4), and the same for moving from 1.5 to 1.6,
so I anticipate this won't be different for moving to 1.7 as baseline.
I personally would not mind waiting for JGroups 5 to move to JDK 7, as
this gives users a bit more time and I won't require JDK 7 before
JGroups 5 anyway, as the NIO2 stuff won't be in JGroups 4, only in 5.
+1 to
stick to 6 at leat till jgroups 5.
Besides NIO2 stuff, is there anything from 7 we want badly?
But if you guys need to move to JDK 7 in Infinispan 6 already, then
that's fine with me, too.
I guess the AS has some requirements, too, so if they decide to move to
JDK 7, then we'll have to make that move too
--
Bela Ban, JGroups lead (http://www.jgroups.org)
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
2:32 a.m.
* ForkJoinPool (assuming we can get AS to inject one)
* AutoCloseable
* Throwable.addSuppressed()
On Fri, May 24, 2013 at 2:01 AM, Mircea Markus <mmarkus(a)redhat.com> wrote:
Sent from my iPhone
On 23 May 2013, at 12:06, Bela Ban <bban(a)redhat.com> wrote:
>
>
> On 5/23/13 12:38 PM, Manik Surtani wrote:
>> Yup, it needs to happen sometime. But the question is, when?
>>
>> Is there anyone out there who desperately needs Infinispan to work on
Java 6?
>
> I got a lot of pushback when I moved the required JDK in JGroups to 1.5
> (people were still using 1.4), and the same for moving from 1.5 to 1.6,
> so I anticipate this won't be different for moving to 1.7 as baseline.
>
> I personally would not mind waiting for JGroups 5 to move to JDK 7, as
> this gives users a bit more time and I won't require JDK 7 before
> JGroups 5 anyway, as the NIO2 stuff won't be in JGroups 4, only in 5.
+1 to stick to 6 at leat till jgroups 5.
Besides NIO2 stuff, is there anything from 7 we want badly?
>
> But if you guys need to move to JDK 7 in Infinispan 6 already, then
> that's fine with me, too.
>
> I guess the AS has some requirements, too, so if they decide to move to
> JDK 7, then we'll have to make that move too
>
> --
> Bela Ban, JGroups lead (http://www.jgroups.org)
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
9:46 a.m.
Support?
On 24 May 2013, at 00:01, Mircea Markus wrote:
Besides NIO2 stuff, is there anything from 7 we want badly?
---
Mark Little
mlittle(a)redhat.com
JBoss, by Red Hat
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor,
Berkshire, SI4 1TE, United Kingdom.
Registered in UK and Wales under Company Registration No. 3798903 Directors: Michael
Cunningham (USA), Charlie Peters (USA), Matt Parsons (USA) and Brendan Lane (Ireland).
9:50 a.m.
On 24 May 2013 15:46, Mark Little <mlittle(a)redhat.com> wrote:
Support?
Don't we support Java6 ?
And people will be very welcome to run on Java7 if they want to, but
we are discussing what the minimum requirement should be.
Sanne
On 24 May 2013, at 00:01, Mircea Markus wrote:
Besides NIO2 stuff, is there anything from 7 we want badly?
---
Mark Little
mlittle(a)redhat.com
JBoss, by Red Hat
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street,
Windsor, Berkshire, SI4 1TE, United Kingdom.
Registered in UK and Wales under Company Registration No. 3798903 Directors:
Michael Cunningham (USA), Charlie Peters (USA), Matt Parsons (USA) and
Brendan Lane (Ireland).
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
11:07 a.m.
/> Besides NIO2 stuff, is there anything from 7 we want badly? /
Yes. In its version 7 release, Java introduces a Socket Direct Protocol
capability. For the first time ever, a Java API can accommodate a direct
bridge to ultra-low-latency physical network providers like Infiniband
(including access to native Infiniband VERBs).
I know this is probably a very limited use case for you guys for right now,
but, Java 7's SDP capability is a game changer. Bela and I have exchanged
musings about this potential to some-time being exposed through the
Infinispan/JGroups API stack(
https://community.jboss.org/message/810754#810754 ). It is something you
guys will definitely want to show case some day (btw, what is a more natural
name marriage than "Infinispan on Infiniband" ?) and with Java 7 SDP
capability you can start building that bridge now.
--
View this message in context:
http://infinispan-developer-list.980875.n3.nabble.com/infinispan-dev-Base...
Sent from the Infinispan Developer List mailing list archive at Nabble.com.
11:19 a.m.
On 5/24/13 6:07 PM, cotton-ben wrote:
/> Besides NIO2 stuff, is there anything from 7 we want badly? /
Yes. In its version 7 release, Java introduces a Socket Direct Protocol
capability. For the first time ever, a Java API can accommodate a direct
bridge to ultra-low-latency physical network providers like Infiniband
(including access to native Infiniband VERBs).
Actually, this should work *without* changes to JGroups or Infinispan
TODAY, if you use JDK 7. According to [1], all you'd have to do is to
use a TCP based configuration, enable SDP sockets instead of TCP sockets
through a system property and provide a config file listing the target
addresses for which SDP sockets shoul be created.
I see that Socket and ServerSocket are already supported, so NIO2 is not
even needed (from an API viewpoint).
I know this is probably a very limited use case for you guys for
right now,
but, Java 7's SDP capability is a game changer. Bela and I have exchanged
musings about this potential to some-time being exposed through the
Infinispan/JGroups API stack(
https://community.jboss.org/message/810754#810754 ). It is something you
guys will definitely want to show case some day (btw, what is a more natural
name marriage than "Infinispan on Infiniband" ?) and with Java 7 SDP
capability you can start building that bridge now.
Unless I'm wrong above, it would be interesting to get some numbers on
running Infinispan/JGroups over Infiniband using SDP sockets. Are you
planning on doing this ?
I'm currently looking at reshuffling and re-prioritizing the JGroups
roadmap, but I don't think JDK 7 will be used in a 4.0 release, possibly
only in a 5.0 release... I'll blog about this shortly.
[1] http://docs.oracle.com/javase/tutorial/sdp/sockets/enable.html
--
Bela Ban, JGroups lead (http://www.jgroups.org)
12:05 p.m.
/all you'd have to do is [...]/
Thanks Bela. I'd love the "you" in the response above to be me, but the
"you" has to be you. I.e. as much as I'd like to build the bridge to the
capability myself, I am not going to be empowered to do this by my clients.
We need a bridge provider. Might I pep-rally a cry of "Infinispan on
Infiniband today!" to encourage you to be that bridge provider? :-)
/> I see that Socket and ServerSocket are already supported, so NIO2 is not
even needed (from an API viewpoint).
/
Absolutely correct! You do not need NIO2. I can get everything from
java.net.Socket. But I must have Java 7.
/> it would be interesting to get some numbers on
running Infinispan/JGroups over Infiniband using SDP sockets. Are you
planning on doing this ? /
Of course, the numbers will be mind-blowing if you are used to only having
physical provider=Ethernet. I'd love to build a Java based POC to exercise
our use-case. However, I can't be the bridge provider to get from Java
application code to Infiniband VERBs. I need JBoss (Infinispan/JGroups) to
be that bridge provider.
We'll patiently wait for when you guys explicitly support IPoIB in
Infinispan/JGroups. And then, off we go. (But with Java 7, as we all know,
this can be done today!)
Thanks again, Bela. Let's keep these musings flowing.
Ben
--
View this message in context:
http://infinispan-developer-list.980875.n3.nabble.com/infinispan-dev-Base...
Sent from the Infinispan Developer List mailing list archive at Nabble.com.
7:38 a.m.
Me, for now
Regards,
Erik
On May 23, 2013, at 6:39 AM, "Manik Surtani" <msurtani(a)redhat.com> wrote:
Yup, it needs to happen sometime. But the question is, when?
Is there anyone out there who desperately needs Infinispan to work on Java 6?
Cheers
Manik
--
Manik Surtani
manik(a)jboss.org
twitter.com/maniksurtani
Platform Architect, JBoss Data Grid
http://red.ht/data-grid
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
8:07 a.m.
What about skipping 7 and waiting for 8?
On May 23, 2013, at 12:38 PM, Manik Surtani <msurtani(a)redhat.com> wrote:
Yup, it needs to happen sometime. But the question is, when?
Is there anyone out there who desperately needs Infinispan to work on Java 6?
Cheers
Manik
--
Manik Surtani
manik(a)jboss.org
twitter.com/maniksurtani
Platform Architect, JBoss Data Grid
http://red.ht/data-grid
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
galder(a)redhat.com
twitter.com/galderz
Project Lead, Escalante
http://escalante.io
Engineer, Infinispan
http://infinispan.org
8:51 a.m.
If the majority of users go directly to 8 from 6, then yes why not. But
if that's not the case, then we can't do it, either...
On 5/23/13 3:07 PM, Galder Zamarreño wrote:
What about skipping 7 and waiting for 8?
On May 23, 2013, at 12:38 PM, Manik Surtani <msurtani(a)redhat.com> wrote:
> Yup, it needs to happen sometime. But the question is, when?
>
> Is there anyone out there who desperately needs Infinispan to work on Java 6?
>
> Cheers
> Manik
--
Bela Ban, JGroups lead (http://www.jgroups.org)
9:49 a.m.
Oracle will support Java 7 at least until March 2015 [1]. And it's very
likely that some people will keep using 7 after that, just like they are
using 6 now. So unless we want to support Java 6 until 2016, I don't think
we can skip 7.
[1] http://www.oracle.com/technetwork/java/eol-135779.html
On Thu, May 23, 2013 at 4:51 PM, Bela Ban <bban(a)redhat.com> wrote:
If the majority of users go directly to 8 from 6, then yes why not.
But
if that's not the case, then we can't do it, either...
On 5/23/13 3:07 PM, Galder Zamarreño wrote:
> What about skipping 7 and waiting for 8?
>
> On May 23, 2013, at 12:38 PM, Manik Surtani <msurtani(a)redhat.com> wrote:
>
>> Yup, it needs to happen sometime. But the question is, when?
>>
>> Is there anyone out there who desperately needs Infinispan to work on
Java 6?
>>
>> Cheers
>> Manik
--
Bela Ban, JGroups lead (http://www.jgroups.org)
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
4028
days inactive
4029
days old
infinispan-dev@lists.jboss.org
15 comments
9 participants
participants (9)
-
Bela Ban -
cotton-ben -
Dan Berindei -
Erik Salter -
Galder Zamarreño -
Manik Surtani -
Mark Little -
Mircea Markus -
Sanne Grinovero