2:13 p.m.
For JBoss Marshalling 1.3, I'm planning on adding a new River protocol
version (3) and phasing out version 1. As far as I'm aware, Infinispan is
using version 2, correct?
By phasing out old versions, I can reduce the number of runtime checks and
improve performance and maintainability. However, going forward, I will
not be removing support for protocol versions which are used in
widely-deployed versions of projects which use it (Infinispan for one).
Thus, as time goes on, expect me to be pinging you guys about your input on
keeping or dropping various protocol versions.
For protocol version 3, I'm looking at some or all of the following features:
- Full Javassist proxy serialization support
- Fast serialization of more collection types
- The JBoss Marshalling "Pair" type
- JDK 6 collection types (Deque, NavigableSet/NavigableMap and their
implementations)
- More collection utility wrapper types, probably including (but not
limited to):
- Collections.checked*()
- Collections.asLifoQueue()
- Collections.nCopies()
- Collections.newSetFromMap()
- Collections.reverseOrder(*)
Please speak up if there are other features that you'd like to see.
--
- DML ☍
5:06 a.m.
On Sat, 27 Feb 2010 21:13:39 +0100, David M. Lloyd
<david.lloyd(a)redhat.com> wrote:
For JBoss Marshalling 1.3, I'm planning on adding a new River
protocol
version (3) and phasing out version 1. As far as I'm aware, Infinispan
is
using version 2, correct?
We use default version, which afaik is indeed 2 in 1.2.0.GA.
By phasing out old versions, I can reduce the number of runtime checks
and
improve performance and maintainability. However, going forward, I will
not be removing support for protocol versions which are used in
widely-deployed versions of projects which use it (Infinispan for one).
Thus, as time goes on, expect me to be pinging you guys about your input
on
keeping or dropping various protocol versions.
For protocol version 3, I'm looking at some or all of the following
features:
- Full Javassist proxy serialization support
- Fast serialization of more collection types
- The JBoss Marshalling "Pair" type
What's this pair type?
- JDK 6 collection types (Deque, NavigableSet/NavigableMap and
their
implementations)
- More collection utility wrapper types, probably including (but not
limited to):
- Collections.checked*()
- Collections.asLifoQueue()
- Collections.nCopies()
- Collections.newSetFromMap()
- Collections.reverseOrder(*)
Please speak up if there are other features that you'd like to see.
Nothing specific comes to my mind right now but I'll keep it mind in case
anything pops up.
Cheers,
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
7:35 a.m.
On 03/02/2010 05:06 AM, Galder Zamarreno wrote:
On Sat, 27 Feb 2010 21:13:39 +0100, David M. Lloyd
<david.lloyd(a)redhat.com> wrote:
> For JBoss Marshalling 1.3, I'm planning on adding a new River protocol
> version (3) and phasing out version 1. As far as I'm aware, Infinispan
> is
> using version 2, correct?
We use default version, which afaik is indeed 2 in 1.2.0.GA.
OK, so you're not specifying 2 explicitly? Or are you negotiating the
version? Because for 1.3, the default version will change to 3, so an
instance running with JBMAR 1.2 won't be able to read messages written by
an instance running with JBMAR 1.3 by default then. You might want to
ensure that you've got a way to set the version somehow, especially as
JBossAS 6 will ship with a JBMAR 1.3.something.
> - Full Javassist proxy serialization support
> - Fast serialization of more collection types
> - The JBoss Marshalling "Pair" type
What's this pair type?
It's a simple serializable class which holds two values of different types.
It uses generics for type-safety as well; each value may be of a
different type. Amazingly handy. :)
Nothing specific comes to my mind right now but I'll keep it mind
in case
anything pops up.
Thanks!
--
- DML ☍
1:36 a.m.
On Tue, 02 Mar 2010 14:35:38 +0100, David M. Lloyd
<david.lloyd(a)redhat.com> wrote:
On 03/02/2010 05:06 AM, Galder Zamarreno wrote:
> On Sat, 27 Feb 2010 21:13:39 +0100, David M. Lloyd
> <david.lloyd(a)redhat.com> wrote:
>
>> For JBoss Marshalling 1.3, I'm planning on adding a new River protocol
>> version (3) and phasing out version 1. As far as I'm aware, Infinispan
>> is
>> using version 2, correct?
>
> We use default version, which afaik is indeed 2 in 1.2.0.GA.
OK, so you're not specifying 2 explicitly? Or are you negotiating the
version? Because for 1.3, the default version will change to 3, so an
instance running with JBMAR 1.2 won't be able to read messages written
by an instance running with JBMAR 1.3 by default then. You might want
to ensure that you've got a way to set the version somehow, especially
as JBossAS 6 will ship with a JBMAR 1.3.something.
Ok, makes sense. I'll explicitly set it to 2. When we move to Infinispan
5.x, we can maybe move it up to 3 which by then JBMAR 1.3 will likely be
out.
>> - Full Javassist proxy serialization support
>> - Fast serialization of more collection types
>> - The JBoss Marshalling "Pair" type
>
> What's this pair type?
It's a simple serializable class which holds two values of different
types. It uses generics for type-safety as well; each value may be of
a different type. Amazingly handy. :)
So that's a serializable tuple then :).
> Nothing specific comes to my mind right now but I'll keep it mind in
> case
> anything pops up.
Thanks!
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
9:14 a.m.
On 03/04/2010 01:36 AM, Galder Zamarreno wrote:
Ok, makes sense. I'll explicitly set it to 2. When we move to
Infinispan
5.x, we can maybe move it up to 3 which by then JBMAR 1.3 will likely be
out.
OK, sounds like a plan.
> It's a simple serializable class which holds two values of
different
> types. It uses generics for type-safety as well; each value may be of
> a different type. Amazingly handy. :)
So that's a serializable tuple then :).
Exactly :)
Thanks, Galder.
--
- DML ☍
5406
days inactive
5411
days old
infinispan-dev@lists.jboss.org
4 comments
2 participants
participants (2)
-
David M. Lloyd -
Galder Zamarreno