Trace: • Object Injection • Functions and Procedures With IN and OUT Parameters • Global Metadata Caching
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
jvx:server:storage:metadata_caching [2020/06/15 11:35] cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation) |
jvx:server:storage:metadata_caching [2020/07/22 13:10] (current) cduncan errant space |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ~~Title: Global Meta Data Caching~~ | + | ~~Title: Global Metadata Caching~~ |
| - | Databooks at the client already allow for the caching of meta data to minimize communication with the server. However, server side storage updates meta data each time data is accessed. During productive use, this is unnecessary overhead that we would prefer to avoid. | + | Databooks at the client already allow for the caching of metadata to minimize communication with the server. However, server-side storage updates metadata each time data is accessed. During productive use, this is unnecessary overhead that we would prefer to avoid. |
| Global metadata caching is configured in the server´s configuration file, config.xml, using the following option: | Global metadata caching is configured in the server´s configuration file, config.xml, using the following option: | ||
| Line 10: | Line 10: | ||
| </file> | </file> | ||
| - | If any metadata is modified while this option is activated, either the application server has to be restarted, or the application context has to be updated, since the cache is static. | + | If any metadata is modified while this option is activated, either the application server has to be restarted, or the application context has to be updated, as the cache is static. |