Good job Smaitha. BTW in the jira you mentioned there are two points to
solve. You have addressed first issue. What happened to the second point.
(Permission Loading)
Thanks Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729
On Wed, Jul 23, 2014 at
On Wed, Jul 23, 2014 at 11:40 AM, Danushka Fernando danush...@wso2.com
wrote:
Good job Smaitha. BTW in the jira you mentioned there are two points to
solve. You have addressed first issue. What happened to the second point.
(Permission Loading)
IIRC permissions are already cached. You can
Hi,
As suggested in [1], Instead of calling ProjectUtils(which is a java class)
directly from jaggery layer, I have exposed those methods as OSGI services
and cached the results. This improvement reduced the page load time of the
most of the pages by approximately 100ms.
[1] -
On Wed, Jul 23, 2014 at 10:32 AM, Samith Dassanayake sam...@wso2.com
wrote:
Hi,
As suggested in [1], Instead of calling ProjectUtils(which is a java
class) directly from jaggery layer, I have exposed those methods as OSGI
services and cached the results. This improvement reduced the page
Hi Samith,
Good job. We need to come up with a strategy to load all the fields with
data at the page load time. At the moment in some pages, fields are loaded
in the UI without any data and it takes a while for the data to load. I
think it is better to load data before the page loads and just
Hi Asanka
Previously it calls ProjectUtils each and every time when the application
requires type of the application. Since the application type is highly
unlikely to change I cached the results(app types) based on the tenant
domain in the session.
On Wed, Jul 23, 2014 at 10:40 AM, Asanka
