Sadly, even thou my application isn't all that smart I've already fallen into that trap - as my test first launches a Jetty process running a compojure app, and fires http calls at it - with the send-sms call being behind compojure.... on another thread.
I'm thinking a different way of handling things might be better - maybe having send-sms just add a message struct to a queue, and only hook up a watcher when in production mode. -- Pull me down under... On Tue, Sep 29, 2009 at 2:20 AM, Laurent PETIT <laurent.pe...@gmail.com>wrote: > But as soon as your application becomes smart enough to do things in > parallel (e.g. create and send an e-mail in a separate thread), just using > dynamic binding in tests may not be enough, still the binding will not be > seen by default by other threads. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
