Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
MIME-Version: 1.0
In-Reply-To: <CAH6wpnrJ0NzvKjvdcgc6qnug1cpu-tairo4vYCOBmV_9VqXNHg@mail.gmail.com>
References: <CAH6wpnrJ0NzvKjvdcgc6qnug1cpu-tairo4vYCOBmV_9VqXNHg@mail.gmail.com>
From: Clebert Suconic <clebert.suconic@gmail.com>
Date: Thu, 9 Feb 2017 08:57:48 -0500
Message-ID: <CAKF+bsq1u-1sMsvDnq0Z7Gu7zc8b51Y2jLm-54MDLpfvb4HpiQ@mail.gmail.com>
Subject: Re: [DISCUSS] ActiveMQ Artemis 2.x stream
To: "dev@activemq.apache.org" <dev@activemq.apache.org>
Content-Type: text/plain; charset=UTF-8
archived-at: Thu, 09 Feb 2017 13:57:56 -0000

I am doing some refactoring on the encoding of messages...


Currently ServerMessage and ClientMessage are too tight with Queue and
the core client, requiring us to always convert messages through the
core message.


That is, if you receive a Message in OpenWire, it is converted back to
the core-message through the converters and when a client comes, it
will convert back to openwire. (same will go through any other
protocols).


I have started this on a personal branch, and I believe I will done in
2 weeks and half time, making good progress...


I will open a dev/DISCUSS thread some time (I believe I had started
one last year already).


clebert

On Thu, Feb 9, 2017 at 7:18 AM, Martyn Taylor <mtaylor@redhat.com> wrote:
> All,
>
> As discussed in a previous thread [1] Artemis master has had a major bump
> (due to major model refactor).
>
> The great news is that the new model is more flexible and lends itself well
> to 5.x features like Virtual Topics as well as being consistent across all
> protocols.  The not so good news is that this work required API breakages,
> hence the major version bump.).  This refactor work (mostly around the
> addressing scheme [2]) is now completed.
>
> The code base is now in a stable state, and as such, I'd like to start
> thinking about doing a release off of master as an Apache Artemis 2.0.0 to
> get the new changes into the hands of users.
>
> I'd like to open discussion around this topic, does anyone have any
> suggestions, or can think of anything that is needed before we go ahead
> with a major release? This is the perfect time to do anything that could
> break APIs, drop deprecated methods support, break data format etc...
>
> Cheers
> Martyn
>
> [1]
> http://activemq.2283324.n4.nabble.com/DISCUSS-Artemis-addressing-improvements-JMS-component-removal-and-potential-2-0-0-td4719262.html
>
> [2] https://issues.apache.org/jira/browse/ARTEMIS-780


-- 
Clebert Suconic