On Feb 3, 11:31 am, Rich Hickey <richhic...@gmail.com> wrote: > One idea is to pass commute-like and deref-like functions to the > handling code for sending change to, and accessing, the session state. > The state will be an immutable value as usual. This encapsulates > everything about the session data.
That's an interesting approach. Would you consider it good or bad practise to inherit the session store from IDeref? Clojure's concurrency primitives have different functions to handle updates (swap!, alter, etc.), but universally use deref to return their contents. Would it be worth following the same convention for sessions? - James -- 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
