lizhanhui commented on PR #84: URL: https://github.com/apache/rocketmq-apis/pull/84#issuecomment-1837001012
It's true that there is some nuance between delay-delivery-message and scheduled-message when time source is considered. But, IMO, we may offer two API for them using the same underlying implementation. Aka, express the concept of delay-delivery through existing `delivery_timestamp` field as [JMS 2.0 Spec](https://www.ibm.com/docs/en/ibm-mq/8.0?topic=functionality-jms-20-delivery-delay) > With JMS 2.0, you can specify a delivery delay when sending a message. The queue manager does not deliver the message until after the specified delivery delay has elapsed. > An application can specify a delivery delay in milliseconds, when it sends a message, by using either MessageProducer.setDeliveryDelay(long deliveryDelay) or JMSProducer.setDeliveryDelay(long deliveryDelay). **This value is added to the time at which the message is sent and gives the earliest time at which any other application can get that message**. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
