Rob,
Are you aware of a way to configure the "Allow Only One Copy of Document in Memory" setting in combination with other settings, perhaps the Document Settings you mentioned, to only keep one active document in memory, but avoid the reload lag that causes the hourglass for users? The use case is a very large document that is reloaded frequently. When the server reloads the new version of the application into RAM, users can't use the application until it's fully loaded. I want something like a third alternative to single copy vs. multiple copy, where the server keeps the old copy in memory until the new copy is loaded, then transfers the server bookmarks and sessions over to the new copy quickly, for minimal user impact. Then flushes the old copy immediately.
