Client-side transient model for storing temporary data

Question

We've been using the ODataModel in our UI5 application for retrieving data from Gateway and now we have a requirement to store temporary (session based) client-side data.  Ideally it would be stored in such a way that it can be shared across views and controllers and can be bound from UI components via property bindings.  The data in most cases will be OData entities.  As an example a user would view a list of PO's (from the ODataModel) in the first view, then select a subset of POs and move onto the next view to "work" on those POs.  We'd want to store this subset of POs in a client model so the second view can bind to the model and display them.
My first thought is to create another model separate from our ODataModel in which we could add transient client-side data (OData entities and custom data) and make it available to all views and controllers in the app.  I realize we could probably also just store such data in global JS variables, however a client-side model seems like a cleaner approach to me.
I'd appreciate any suggestions on how this can be achieved.

Answer 1

Hi Derek,
why don't you just use sap.ui.core.Core.setModel? You can store multiple models and access them in your entire SAPUI5 app.
Except for SAPUI5-apps, these requirements are often realized with HTML5 Web Storage JavaScript API. As you can see in the following blog post, you can easily store even complex entities and access your items in the entire web-application: Client-side Session Management.
I can't recommend the approach with global variables. A lot of developers had negative experiences with this design pattern. At least, use namespacing techniques to store your functions and variables in one central scope. I've written a simple example on jsFiddle to show you this. As you can see, you could also handle your transient model as an additional variable of your own namespace.
Regards Michael