Hi Michael, We're in a very similar situation to yours. Here's what we did:
1. 2 back end storage impls rah.storage1, rah.storage2 - these are "private" nses. 2. a single storage interface rah.storage for the rest of the business code. At runtime this decides which of storage1 or 2 to call. 3. Now you can implement 2. in many ways, protocol, multimethods, global vars etc. We chose multimethods + macros to generate defmethod calls automatically. @ Laurent, Ken, Why not wrap the entry point in bound-fn ? Convenience? -- 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
