This looks like you are using your HTTP service to store state. HTTP is traditionally a stateless protocol (see http://en.wikipedia.org/wiki/Stateless_protocol ). There are certainly counterexamples to be found, both in open source projects and in commercial applications in production. HTTP purists would attempt to push this kind of state to the client, using cookies or some other client storage mechanism. Is there a reason you are not storing this kind of state in the client?