By the way, in a speech at November's Clojure/conj, some guy remarked that queues are good, and the mere fact that he hadn't found it necessary for Clojure to wrap them shouldn't signal that there's something wrong with them. When a queue would help, use a queue.
In your application... well, suppose that as a hedge against being enlisted to spam innocent victims, you wanted to rate-limit the email transmission. You might use the agent send-off in the transaction, not to send email directly, but rather to enqueue a reminder to send email eventually, and meanwhile a single rate-limited loop would work the queue. -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
