5

I have a need to maintain global state on the server across different browser / user sessions.

My assumption here is that all atoms etc created when a request comes in is specific to that request. Once the response is returned all that state is destroyed and memory freed. Please correct me if I am wrong.

State across requests for a specific session can be maintained in memory by using the session middleware.

However how do I maintain the state across multiple user sessions and requests. If possible I would like to avoid the usage of memcached / redis etc for storing it externally. Is it possible to achieve it in memory itself?

David J.
  • 31,569
  • 22
  • 122
  • 174
murtaza52
  • 46,887
  • 28
  • 84
  • 120

1 Answers1

8

Do you mean that you want global state that is shared across all sessions?

If so than that is easy, just declare an atom or ref in any namespace you like and it will be shared across all sessions, e.g.:

(def my-state (atom {:foo 1 :bar 2}))

This works because the Clojure environment persists for as long as the application server keeps running, and any future requests will be able to observe / modify the global state.

Having said all that - it is worth remembering that global state is often a design smell. You should think about whether you really need this, or if you should consider some other alternative (e.g. pushing the shared state out into a database).

mikera
  • 105,238
  • 25
  • 256
  • 415
  • Thanks for the quick response. @mikera conversely is there also any other type of state that remains confined to the request? I am referring to the servelet level state that is confined to user requests in java. – murtaza52 Sep 13 '12 at 10:39
  • 1
    There's no mutable state that is limited to the request in ring since you almost never need it. Ring middleware that passes/handles modified request maps is the usual approach to request-specific state. – Joost Diepenmaat Sep 13 '12 at 11:57