Hi Samith, Currently Jaggery does not have a caching layer implemented. As a workaround you may use 'application'[01] and 'session'[02] depending on the data you need to cache.
You can keep logged in user specific stuff in the session and global stuff under application context. This approach is recommended if the data you are going to keep in the cache is not heavyweight. However, It is not recommended to keep objects in the application object as they might introduce issues under concurrent environments. It is safe to keep, either java objects or javascript, strings, number etc. [01] http://jaggeryjs.org/documentation.jag?api=application [02] http://jaggeryjs.org/documentation.jag?api=session On Fri, Oct 17, 2014 at 12:21 PM, Samith Dassanayake <[email protected]> wrote: > Hi all, > > I'm working on [1], where we have to cache the data in jaggery layer. Do > we have a cache implementation in Jaggery? If it is, where can I find > documentation? > > [1] https://wso2.org/jira/browse/APPFAC-2396 > > Thanks, > Samith > > -- > Best Regards > > Samith Dassanayake > Software Engineer, WSO2 Inc. > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> 20, Palmgrove Avenue, Colombo 3 E-Mail: [email protected] <[email protected]>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
