Warning: This page has not been updated in over over a year and may be outdated or deprecated.
configuration:record_caching
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
| configuration:record_caching [2016/01/08 08:57] – [Setting Up Caching] emaijala | configuration:record_caching [2016/01/08 13:25] – [Record Caching] demiankatz | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| Starting with release 3.0, VuFind supports the option of storing records from search backends in the local database. This is primarily designed to ensure that user favorite lists remain functional and performant even when search providers are slow or records are deleted; however, it may have additional applications as well. | Starting with release 3.0, VuFind supports the option of storing records from search backends in the local database. This is primarily designed to ensure that user favorite lists remain functional and performant even when search providers are slow or records are deleted; however, it may have additional applications as well. | ||
| + | :!: Not all search backends are supported by cache -- in particular, backends that return different record data when a user is logged in vs. logged out, or on vs. off campus, cannot be reliably cached. | ||
| ===== Setting Up Caching ===== | ===== Setting Up Caching ===== | ||
configuration/record_caching.txt · Last modified: 2020/09/22 14:27 by demiankatz