2 Replies Latest reply on Feb 16, 2011 3:56 PM by Clebert Suconic

    Pool about Scheduled Deliveries

    Clebert Suconic Master

      Current scheduled deliveries are sent with no ordering guarantees, and at the top of the queue. Say, if you sent 10000 regular messages  (i.e. no scheduling), and 1 scheduled delivery to be delivered in 1 second, that scheduled message will jump ahead of the other 10000 messages.

       

       

      For that I'm changing the behaviour to always send to the back of the queue as any other regular send would do. Just being scheduled.

       

      This would be an issue only when messages are building up and there are no consumers on the queue.

       

       

      Is there any user who actually think that scheduled deliveries should take precedence over regular messages? I'm looking for a concrete use case where this would actually be required.

       

       

      Most of the use cases I thought about scheduled deliveries involved a dedicated queue for scheduling.

        • 1. Pool about Scheduled Deliveries
          Clebert Suconic Master

          I'm adding a feature request for a better scheduling BTW.

          • 2. Pool about Scheduled Deliveries
            Clebert Suconic Master

            Clebert Suconic wrote:

             

            Current scheduled deliveries are sent with no ordering guarantees, and at the top of the queue. Say, if you sent 10000 regular messages  (i.e. no scheduling), and 1 scheduled delivery to be delivered in 1 second, that scheduled message will jump ahead of the other 10000 messages.

             

             

            For that I'm changing the behaviour to always send to the back of the queue as any other regular send would do. Just being scheduled.

             

            This would be an issue only when messages are building up and there are no consumers on the queue.

             

             

            Is there any user who actually think that scheduled deliveries should take precedence over regular messages? I'm looking for a concrete use case where this would actually be required.

             

             

            Most of the use cases I thought about scheduled deliveries involved a dedicated queue for scheduling.

            Actually I take it back. if we always add to the tail, redeliveries will be added to the back of the queue, what's wrong.

             

            I'm just improving the ordering when you have multiple deliveries at the same time, but I will not change the ordering semantics we have in place now.