On Jan 7, 2015, at 10:21 AM, Allen Rohner <aroh...@gmail.com> wrote: > As a design rule, I prefer making I/O fns (things that hit the DB or a REST > API), 'dumb', and perform all logic/processing in fns that just receive plain > data, and return plain data.
I’m curious: do you have wrapper functions for the DB reads/writes (i.e., a domain layer that just wraps the calls to your persistence library as well as managing the connections etc)? Currently we primarily run Clojure as the embedded "Model" in a legacy MVC app so we can’t really use Stuart’s Component (at least, I don’t think we can, because we have a lot of entry points into the Clojure code) but we would like to figure out a cleaner way to separate DB access from our business logic on a per request basis... Sean Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "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 --- 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/d/optout.