Evening all.

I need a suggestion.  I have an application that will make very heavy use of Atlas to commnicate to the web server.  Calls to the web server will access a small set of objects, and return one or more calculated values.

For performance reasons, I don't want to re constitute the objects on every AJAX call.  So I'd like them to hang in memory.  Also, I'd like mulitiple users to access the same varibles. My top level object will be a collection of some kind.  I'll have a back ground process that will monitor and remove from the collection, inactive items.

I don't want to use caching, because i need to have instant access for changes made by one user, to any other user that is working with the same oject in the collection.

I was thinking application objects, but am unsure what the issues with this would be.

Suggestions????

Thanks,

Steve