Abstract: Both search criteria and a friends list associated with a user are obtained. One or more data items that satisfy the search criteria are identified as search results. An order of the search results is adjusted based at least in part on multiple additional friends lists, each of which is associated with a data item of the one or more data items. Each of the multiple additional friends lists can also be updated to reflect changes in the friends lists made by users associated with the friends lists.

Abstract: Both search criteria and a friends list associated with a user are obtained. One or more data items that satisfy the search criteria are identified as search results. An order of the search results is adjusted based at least in part on multiple additional friends lists, each of which is associated with a data item of the one or more data items. Each of the multiple additional friends lists can also be updated to reflect changes in the friends lists made by users associated with the friends lists.

Abstract: Both search criteria and a friends list associated with a user are obtained. One or more data items that satisfy the search criteria are identified as search results. An order of the search results is adjusted based at least in part on multiple additional friends lists, each of which is associated with a data item of the one or more data items. Each of the multiple additional friends lists can also be updated to reflect changes in the friends lists made by users associated with the friends lists.

Abstract: Both search criteria and a friends list associated with a user are obtained. One or more data items that satisfy the search criteria are identified as search results. An order of the search results is adjusted based at least in part on multiple additional friends lists, each of which is associated with a data item of the one or more data items. Each of the multiple additional friends lists can also be updated to reflect changes in the friends lists made by users associated with the friends lists.

Abstract: Architecture for security trimming results in a document version environment. Versioned documents are stored with metadata that includes associated access rights. All versions are searched using multiple user accounts of varying levels of access that correspond to the document versions. Result sets are returned for each user account and trimmed during a merge process by considering the user rights associated with each of multiple versions of objects or documents. Each document metadata includes a scope ID that defines security rights for that document. In a two-version document (major and minor) implementation, successive queries are run as a user with rights to all minor versions, and as a user with rights to all major items, but not the minor items. The result sets are merged into a final trimmed result set by examining the rights to each item in the versioned sets that align with rights of the current user.

Abstract: A web page is generated by locating an area in a website to place the page and selecting a template for the page. An output cache manager allows a user to attach a cache profile in the form of metadata to the template and the area in the website. The output cache manager uses the metadata to identify the cache profile that is associated with the web page when the page is rendered. The cache profile identifies the page output directive caching parameters that are associated with a web page when the page is rendered. A cache profile may be inherited by web pages that are dependent on the site in which the page resides such that a previously established cache profile is overridden. The cache profile may be created and modified by any authorized user. Any modification to the cache profile may be applied to all web pages that are associated with the cache profile.

Abstract: Architecture for security trimming results in a document version environment. Versioned documents are stored with metadata that includes associated access rights. All versions are searched using multiple user accounts of varying levels of access that correspond to the document versions. Result sets are returned for each user account and trimmed during a merge process by considering the user rights associated with each of multiple versions of objects or documents. Each document metadata includes a scope ID that defines security rights for that document. In a two-version document (major and minor) implementation, successive queries are run as a user with rights to all minor versions, and as a user with rights to all major items, but not the minor items. The result sets are merged into a final trimmed result set by examining the rights to each item in the versioned sets that align with rights of the current user.