![]() The object cache then checks the access control lists (ACLs) for the user who initiated the request and returns the appropriate results to that user based on whether that user can see draft items. The results for the Portal Super User account include draft items, and the results for the Portal Super Reader account include only published items. The results of these two queries are stored in the object cache. ![]() When a publishing control requests the object cache to make a query to get data for the control, the cache makes the query, not as the user making the request, but instead it makes the query twice: once as the Portal Super User account and once as the Portal Super Reader account. To optimize the cache hit rate and memory requirements, the queries must be based on whether a user can see draft items. These results are cached based on the user making the query. Various parts of the publishing feature make queries for which the results are cached in the object cache. In SharePoint Server, querying for items is linked with the user account that makes the query. For information about the object cache, see Cache settings operations in SharePoint Server. This article explains why these object cache user accounts must be configured and describes how to configure the accounts. ![]() The Portal Super User and Portal Super Reader accounts must be separate accounts, and they must not be accounts that will ever be used to log in to the site.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |