Whatever you guys chose, do not go the immutable road. Compojure took that approach and now many people (including me) are stuck with situations where they need to update session in a middle and pass it somewhere else, and they can't. Session is a data storage, just like a database.
One of the strong points of compojure is the layers of middleware. Unfortunately there's no way to communicate between the layers, because current session updating mechanism makes it impossible. You cannot use the session to signal to the middleware that this particular case requires different handling. So one has to resort to communicating through other shared data storages like database and then practically duplicate the session mechanism. -- 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
