On Tue, Oct 21, 2014 at 8:34 AM, Jamie Lennox <[email protected]> wrote:
> The only reason is that I didn't want to introduce a global variable cache > in a library. The session should be a fairly long running object and i'm > looking at ways we could serialize it to allow horizon/CLIs to manage it > themselves. > > A quicker way would be to make the discovery cache an actual object and > allow horizon/CLIs to handle that seperately to the session/auth plugin. I > don't know which they would prefer. We need a generalized caching layer in all of the clients, a session/auth cache is just another instance of that. I've been working under the assumption for OSC that I'd be doing most of that work and that it would live in OSC initially. I like the idea of a cache object that the app subclasses and hands back to the Session, then anything using the Session can make the callbacks. dt -- Dean Troyer [email protected]
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
