[jira] [Comment Edited] (ARTEMIS-869) Extend DeliveryMode to add a "LAZY_PERSISTENCE" option

["clebert suconic (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722863#comment-15722863 ] 

clebert suconic edited comment on ARTEMIS-869 at 12/5/16 5:53 PM:
------------------------------------------------------------------

experienced JMS Users are already used to special deliveryMode... e.g: Tibco: https://docs.tibco.com/pub/enterprise_message_service/7.0.1-march-2013/doc/html/tib_ems_api_reference/api/javadoc/com/tibco/tibjms/Tibjms.html

the user will have to read the manual of course, but the API would make it more explicit on the need.

I just think that makes an optional and easy thing for users to get access to the feature. I think this would only aggregate value to the user. There's no detriment here.

It's just a better API I think.

Only possibility would be some incompatibility with the Spec (requiring us to throw an exception).  Which is easy to be checked.


was (Author: clebertsuconic):
experienced JMS Users are already used to special deliveryMode... e.g: Tibco: https://docs.tibco.com/pub/enterprise_message_service/7.0.1-march-2013/doc/html/tib_ems_api_reference/api/javadoc/com/tibco/tibjms/Tibjms.html


I just think that makes an optional and easy thing for users to get access to the feature. I think this would only aggregate value to the user. There's no detriment here.


Only possibility would be some incompatibility with the Spec (requiring us to throw an exception).  Which is easy to be checked.

> 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)