Yup, I think the transactional semantics are the main cause of this behavior. Aren't send and send-off doing the same thing during a "real" transaction in a ref? To fight the issue of repeating send if the transaction gets retried.
On Wed, Jun 16, 2010 at 1:05 PM, Meikel Brandmeyer <m...@kotka.de> wrote: > Hi, > > On Jun 16, 12:56 pm, Rasmus Svensson <r...@lysator.liu.se> wrote: > >> One solution to the sleep problem could perhaps be to let the agent send >> this to it self: >> >> (fn [state millis] >> (Thread/sleep millis) >> state) > > With this one has to keep in mind, that maybe someone else has already > sent another action to the agent. So the sleep might happen after some > further computation and not immediately. > > Sincerely > Meikel > > -- > 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 -- Moritz Ulrich Programmer, Student, Almost normal Guy http://www.google.com/profiles/ulrich.moritz -- 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
