On Sun, Sep 11, 2011 at 1:29 AM, Laurent PETIT <laurent.pe...@gmail.com> wrote: > now that I've stepped back a little bit and acknowledged my ignorance (while > working on it : currently reading "Java concurrency in practice" :-) )
Kevin pulled me up on this too (in IRC) and pointed me at the Java solution. As it happened I decided to avoid an async solution in the end (the speed up wasn't worth the complexity of adding concurrency in my situation - which I didn't know for sure until I'd tried both approaches). > This remains me of the "viscosity" smell : if it's way easier to do the > wrong thing than it is to do the right thing, expect people to do the wrong > one. Yes, it seems that this is a common enough need that it would be nice to have an idiomatic Clojure library to implement this, perhaps as part of new contrib? Kevin, I'd be particularly interested in your thoughts on that since I understand you feel the Java solution is already pretty clean and simple? -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ World Singles, LLC. -- http://worldsingles.com/ Railo Technologies, Inc. -- http://www.getrailo.com/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880) -- 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
