I have an application that needs to route all changes through a single server so that every client sees everything in the same sequence. The scale is small enough that a single server is not an unreasonable limitation. The same server also persists the data.

It seems like the simplest cacheing model is to just leave a Session around for the entire duration of the server, calling disconnect() whenever things get quiet. This is the extended session pattern, but with an extreme definition of "extended."

Are there pitfalls to this that are not apparent?

Thanks.

(It sure seems like this should have been discussed previously somewhere, but I haven't been able to find anything on it. Pointers to previous threads would be appreciated, as well, of course, as direct answers.)