Bug 810540

Summary: [gui] logging out should clear the ResourceType cache
Product: [Other] RHQ Project Reporter: Ian Springer <ian.springer>
Component: Core UIAssignee: Ian Springer <ian.springer>
Status: CLOSED DEFERRED QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.3CC: ccrouch, hrupp, jshaughn
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-26 21:17:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ian Springer 2012-04-06 15:17:39 UTC 
Currently if existing ResourceTypes are updated as part of a plugin update, the updates do not get picked up by the GUI, because the GUI's cache contains the old types. This is fine, except the only way for the user to get the types updated in the GUI except is to do a hard browser refresh. This is not very intuitive and causes the user to have to wait several seconds for the page to load. Logging out should also clear the type cache. Then we can say in the documentation, "if you update any Agent plugins, to pick up the changes in the GUI, log out and then log back in.
Comment 1 Charles Crouch 2012-04-09 14:28:34 UTC 
Not sure I agree that the cache should be cleared on log out, since changes to 
ResourceTypes should in general be pretty rare in production deployments, e.g. 
upgrading to new JON versions, patches, new customer developed plugins. It 
seems a waste to have people download that extra data (presumably is a lot?) on 
every login. I agree its not great that it requires a hard refresh right now, 
this is less good because not every user is going to know that they need to do 
that.

I would say we need a way to invalidate the ResourceType cache in the browser 
when it needs to be updated, rather than a blanket cache eviction policy.
Comment 2 Jay Shaughnessy 2013-02-26 21:17:11 UTC 
Closing this.  If and when we get server2gui notification we'll take care of this as part of that work.