[ 
https://issues.apache.org/jira/browse/AMQ-9455?focusedWorklogId=921233&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-921233
 ]

ASF GitHub Bot logged work on AMQ-9455:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 29/May/24 14:36
            Start Date: 29/May/24 14:36
    Worklog Time Spent: 10m 
      Work Description: cshannon commented on PR #1182:
URL: https://github.com/apache/activemq/pull/1182#issuecomment-2137575544

   It's not really clear to me when I first read this what MessageStrategy was 
supposed to be from the name so I'm wondering if we should rename it. if this 
is supposed to be essentially an interceptor framework to mutate a message the 
maybe we just call it something like MessageInterceptor. However, I know we 
used the term "Strategy" elsewhere 
   
   Also, the API may need some discussion. A lot of times with something like 
this you might want to return the message so you can chain it and actually 
return an entirely different object, but this could have its own problems with 
things like potential memory usage not being tracked correctly. This only 
supports mutating in place which can have problems as well.
   
   Anyways, the main thing is just making sure the public API is well thought 
out, named well, decide if we want to allow mutating in place only or not, etc 
because once it's out there it's hard to change it as people will create 
implementations.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 921233)
    Time Spent: 20m  (was: 10m)

> DestinationPolicy to support MessageStrategy
> --------------------------------------------
>
>                 Key: AMQ-9455
>                 URL: https://issues.apache.org/jira/browse/AMQ-9455
>             Project: ActiveMQ Classic
>          Issue Type: New Feature
>            Reporter: Matt Pavlovich
>            Assignee: Matt Pavlovich
>            Priority: Major
>             Fix For: 6.2.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> A configurable list of message policy entries that will all for message 
> enrichment and enforcement of message content policies.
> This feature would serve to replace broker-wide plugins:
> ForcePersistencyModeBrokerPlugin
> TimeStampingBrokerPLugin
> UserIDBroker



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact


Reply via email to