+1 to adopt APR.
As 4.2 has a a different store format for some store implementations
(Kaha/rapid/quick) and we need to introduce a new default store to
maintain performance with persistent cursors, plus the change from
JRE 1.4 to JRE 1.5, the next release should be version 5.0
cheers,
R
On Jan 23, 2007, at 10:35 AM, Guillaume Nodet wrote:
I am under the impression that the open wire protocol should
always be able to maintain backward compatibility.
Does this mean that we will never change the major version ;-)
That is okay by me! If we stop using major to represent wire forma
yes. trunk has already tossed backport-util-concurrent
On 1/23/07, Christopher G. Stach II <[EMAIL PROTECTED]> wrote:
Rob Davies wrote:
> Hi Brian,
>
> this isn't exactly true - we have always incremented the major version
> number with wire protocol changes when they are not backward compatibl
Rob Davies wrote:
> Hi Brian,
>
> this isn't exactly true - we have always incremented the major version
> number with wire protocol changes when they are not backward compatible
> - but it's erroneous to assume that there is a casual link between the
> two - its just been coincidental to date.
>
Hi Brian,
this isn't exactly true - we have always incremented the major
version number with wire protocol changes when they are not backward
compatible - but it's erroneous to assume that there is a casual link
between the two - its just been coincidental to date.
cheers,
Rob
On 23 Jan
This is a good point. The new openwire should be able to always stay
backwards compatible so the old model of revving the major number when
the wire protocol breaks might not be right anymore.
On 1/23/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
I am under the impression that the open wire pro
I am under the impression that the open wire protocol should
always be able to maintain backward compatibility.
Does this mean that we will never change the major version ;-)
On 1/23/07, Brian McCallister <[EMAIL PROTECTED]> wrote:
On Jan 23, 2007, at 9:15 AM, Rob Davies wrote:
> The latest de
On Jan 23, 2007, at 9:15 AM, Rob Davies wrote:
The latest development is being done on ActiveMQ 4.2 - however
there are a lot of improvements between 4.1 and 4.2 - namely:
1. Use of Java 5
2. Message cursors for persistent messages
3. Spooling of temporary messages id broker memory is full
