New answers tagged cache
Not knowing entirely how your page functions and how the widgets work, another option would be to store it using the local storage capabilities of the browser. I have used this in cases to store user locations, list names, and other things so they don't have to be repeatedly fetched from the UPS or other sources. There is a JS library called store.js that ...
Since you are looking for local variables with respect to code , go for sessions. dispose all objects implement best practise for caml query to load splist and doc lib. Use SpMonitor and see the performance results in developer dashboard. If you still face issue with performance , then see if disributed cache suits your farm or no .
I have noted the common issues and solutions w.r.t distributedcache http://sharepointjournal.com/2014/08/19/sharepoint-2013-distributed-cache-boon-or-bane/
SharePoint doesn't need the password because its not actually authenticating anywhere with these accounts. SharePoint uses administrative and service accounts to fetch information and content from the the SharePoint databases. It checks its own internal access control lists (permissions) to determine the level of access an account has on an object - from no ...
SuperUser and SuperReader accounts are normal account not services accounts that's why these are not managed accounts. SharePoint use these accounts to cache the data impersonating the App Pool Account. these accounts required Policy of web app level permissions and just grab the data from data base and put it into object cache. So when user make a request, ...
Top 50 recent answers are included