WIP: Hook cache up to the charmbrowser and charm details views 

I don't really see it as a problem. If you're using a model in a cache you have to be able to handle the case where it's no longer there. At the moment the only time the cache is thoroughly emptied is on browser destroy. 

The only way around this is to use the charm cache in the db as it's never emptied.