What is a good way to store large temporary “session” data in a web application
My company has a 3rd party web service we are designing a front end for. The "objects" used by this web service are very large (and variable depending on the number of sub-entities created). The web service does not expose methods to commit/load sub-entities, only the full object hierarchy. The UI itself is split into many sub screens, and master/detail views to be able to efficiently/easily edit the large amount of data. The issue is where to store all the data you aren't currently looking at. Doing the web service commit takes up to 30 seconds for large records, so it is not feasible to use