I don't think it's the correct approach to cache in controllers. It should be done
in the service (angular). Also would it not be an idea to use the cache mechanism already
provided by http? Alternatively it could use angulars built in cache mechanism
(
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Monday, 5 August, 2013 1:49:50 PM
Subject: Re: [keycloak-dev] need to cache REST calls
"require to down" == "request to download"
On 8/5/2013 8:48 AM, Bill Burke wrote:
> IMO, the admin UI makes too many REST calls that will make the UI both
> slow and increase load on the backend. We should fix this after the 1st
> iteration of the admin UI. When the GlblCtrl initializes it should make
> one big REST require to down everything that makes sense in the first go
> and cache it in a global scope. (i.e. everything but users and
> role/scope mappings). UI components should render and link their models
> to variables in the global scope. I've already had to do this to make
> the realm-switching select box I added work in an integrated fashion.
>
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev