```
@ProviderType
public interface ModelCache
```
The Model Cache allows an instance of model to be cached for the life of the Sling HTTP Request. This is convenient when using Sling Models across components when the models are always the same in the context of the Sling HTTP Request (such as the ASC Config or PagePredicate) or when a model should only be instantiated once per request (such as the Search model). The way the ModelCache is typically used is in an HTL script and the ModelCache model is retrieved normally via the data-sly-use.modelCache call such as data-sly-use.modelCache="com.adobe.aem.commons.assetshare.util.ModelCache" Cache-able models are then gotten using the Sling Model’s adapter class name, by passing it as a String to the modelCache object’s get method via the [..] operator, such as: data-sly-test.config="${modelCache['com.adobe.aem.commons.assetshare.configuration.Config']}" If in some circumstance a “fresh” (not from cache) instance of a Sling Model is desired, simply use data-sly-use.myModel="com...SomeModel" as usual, and simply do not engage the ModelCache. Considerations: - If the requested model does not exist in the ModelCache, it will be adapted from the SlingHttpServletRequest, cached and returned to the requesting code. - Cache-able models MUST be adaptable from SlingHttpServletRequest. - Only ONE instance of a particular Sling Model Class type can exist in the cache (for that request).

All Methods Instance Methods Abstract Methods
Modifier and Type	Method	Description
`<T> T`	`get(Class<T> clazz)`	This method is preferred from use in Java code where classes can explicitly provided.
`Object`	`get(Object className)`	This method is preferred from use in HTL code where classes can NOT explicitly provided, but Strings can be easily passed.

Interface ModelCache