Hi Matt

I think we should be driven by feature more than time.

So we are not in the rush.

Regards
JB

Le lun. 31 mars 2025 à 21:56, Matt Pavlovich <mattr...@apache.org> a écrit :

> JB-
>
> What timeframe did you have in mind?
>
> Previously, we had discussed re-working to use the new openwire project as
> the basis for adding shared topic subscription support going forward.
>
> Given the recent Apache security push, I think it would be wise to bite
> off the new openwire project structure in v6.2.0.
>
> Both delivery delay and shared topic subscriptions probably need a new
> protocol version to do that correctly. My first pass at DeliveryDelay was
> to re-use existing scheduling support property, but there is wonkyness in
> doing that as properties are added/removed etc.
>
> Suggested proposal—
>
> Short term v6.2.0:
>    receiveBody and completionListener relatively soon.
>    DeliveryDelay (using properties)
>    (Integrate new openwire project here?)
>
> Medium term: v6.3.0:
>    (Requires openwire project update and v13 protocol)
>    DeliveryDelay (using openwire protocol)
>    Shared Topic Subscriptions
>
> I believe Chris is on holiday, and we should give him time to chime in
> before firming up the plan.
>
> Thanks,
> Matt Pavlovich
>
> > On Mar 31, 2025, at 2:26 AM, Jean-Baptiste Onofré <j...@nanthrax.net>
> wrote:
> >
> > Hi guys
> >
> > Now that we did a run of new ActiveMQ Classic releases
> > (6.1/5.19/5.18/etc), I propose to focus on 6.2.0.
> >
> > The purpose is to include new JMS3 features support. We have the
> > following "pending" features:
> > - receiveBody(Class)
> > - DeliveryDelay
> > - Completion listener async send support
> > - Shared topic consumers
> >
> > I'm resuming my work on receiveBody() on the client, targeting to
> > include that in 6.2.0 (starting by creating a design proposal PR).
> >
> > Does anyone plan to work on the other items ?
> >
> > Regards
> > JB
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@activemq.apache.org
> > For additional commands, e-mail: dev-h...@activemq.apache.org
> > For further information, visit: https://activemq.apache.org/contact
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@activemq.apache.org
> For additional commands, e-mail: dev-h...@activemq.apache.org
> For further information, visit: https://activemq.apache.org/contact
>
>
>

Reply via email to