Hey James,
That works as long as there is only one thing with side-effects. In the
above example I could e.g have the sending of the email logged and so I can
no longer use this method. What I'd like to see is whether the top-level
construct -wrapping the sending of the email by an agent in a
On 2013-02-20, at 9:32 AM, Balint Erdi balint.e...@gmail.com wrote:
In the languages I come from (e.g Ruby) I'd use a library that handles the
queueing and consumption of tasks. Is this how you'd do it in Clojure or it's
one of these cases where Clojure itself suffices where other languages
Hey,
So yesterday we discussed concurrency at our meetup
(http://www.meetup.com/Budapest-Clojure-User-Group/) and a question occurred to
me.
Suppose we have a classic web application. (I'm not currently building such a
web app in Clojure, so that's a theoretical question).
When the user
I can't find the reference now, but either in a screencast or a discussion
I read it was mentioned that if you have a single thing that performs
side-effects, you can perform this function last in the transaction without
worrying about any issues. The reasoning here is that if anything before
