Best Practices - IronMQ #84

Open
frommww opened this Issue Apr 21, 2012 · 2 comments

Comments

Projects
None yet
3 participants
@frommww
Contributor

frommww commented Apr 21, 2012

Include best practices on getting data from IronMQ.

User:
Also, so are you saying it is not a best practice to read the queue size and loop over it? Rather it is better to simply read it and see if you get anything... I think I'm answering my own question...

Ken F.
Not wise to use queue size. just read and it'll return an empty queue message.
then you can sleep or adjust a scheduled task accordingly.
that's our fault for not including best practices on using queues.

@ghost ghost assigned paddycarver Apr 23, 2012

@treeder

This comment has been minimized.

Show comment
Hide comment
@treeder

treeder Apr 23, 2012

Contributor

+1, this would be very helpful stuff.

Contributor

treeder commented Apr 23, 2012

+1, this would be very helpful stuff.

@paddycarver

This comment has been minimized.

Show comment
Hide comment
@paddycarver

paddycarver Apr 23, 2015

Contributor

Would it be possible unassign me from this issue, or close the issue?

Contributor

paddycarver commented Apr 23, 2015

Would it be possible unassign me from this issue, or close the issue?

@paddycarver paddycarver removed their assignment Apr 23, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment