Well @jobara my idea was that GPII would be queried for the currently logged user only once, when the GPIISession component is created and would be "cached" in there. Any other component that would need access to this information would have to access GPIISession's options and know about the currently logged user. The reason for this was to minimize network traffic with the server, anticipating that during the lifetime of a session component the currently logged user would not change. Such a change would demand a re-instantiation of the session component, which means a refresh of the page. Do you suggest i revert the "caching" functionality and let any component that wants to know about the currently logged user query GPII directly every time?