[
https://issues.apache.org/jira/browse/ARTEMIS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15725862#comment-15725862
]
Matt Pavlovich commented on ARTEMIS-869:
----------------------------------------
Discussed on IRC..
Two approaches:
1. Implement an extended class ActiveMQDeliveryMode (ActiveMQ 5.x-like
ActiveMQSession.INDIVIDUAL_ACKNOWLEDGEMENT)
2. Extend the ActiveMQJMSConstants class (Artemis uses for
INDIVIDUAL_ACKNOWLEDGEMENT)
> Extend DeliveryMode to add a "LAZY_PERSISTENCE" option
> ------------------------------------------------------
>
> Key: ARTEMIS-869
> URL: https://issues.apache.org/jira/browse/ARTEMIS-869
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Reporter: Matt Pavlovich
>
> Currently the JMS Spec defines two delivery modes-- NON_PERSISTENT and
> PERSISTENT. Similar to how the ACK modes have been extended, it would be
> handy to extend the DeliveryMode to support a Kafka-like use case where the
> message should be persisted, but not require a sync() before being ack'd.
> Currently, the only way to define this in ActiveMQ 5.x is the periodic option
> on KahaDB, which effects all messages. It would be handy to be able to also
> define it at the per-message level
> Ideas on option:
> ActiveMQDeliveryMode.LAZY_PERSISTENCE
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
