This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author davin
Recipients Semi, aptrishu, davin, rhettinger
Date 2017-03-04.15:45:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1488642310.76.0.599921579942.issue29454@psf.upfronthosting.co.za>
In-reply-to
Content
My understanding of other message queueing systems is that many are motivated by speed to the point that they will permit messages to be "lost" due to specific scenarios that would be overly costly to defend against.  Other message queueing systems adopt a philosophy that no message should ever be lost but as a compromise to speed do not promise that a message will be immediately recovered when caught in one of these problematic scenarios, only that it will eventually be recovered and processed fully.

It appears that the philosophy adopted or really the solution requirements lead to different best practices.
History
Date User Action Args
2017-03-04 15:45:10davinsetrecipients: + davin, rhettinger, Semi, aptrishu
2017-03-04 15:45:10davinsetmessageid: <1488642310.76.0.599921579942.issue29454@psf.upfronthosting.co.za>
2017-03-04 15:45:10davinlinkissue29454 messages
2017-03-04 15:45:10davincreate