Ideas for how to implement a "user info cache"

[JacobCallahan]

With some concepts being floated around to rbac changes in the AnsibleTower provider, it may become necessary to store information about a user's access to things like workflows, inventories, and more. Constantly looking these up be a significant toll on the provider. Instead, it would likely be smart to implement some form of local cache to store the information after initial lookup.

Here are some things I think are important for the design of this feature.

1. Ease of hooking into the cache for provider classes
2. Automatic and manual cache invalidation
3. multi-thread/process safe read/write
4. easily extensible
5. fast/light

I'll follow-up with additional design ideas in responses to this discussion.