return relatedContentBhv.selectByPK(id);
    }

    /**
     * Stores (inserts or updates) a related content entity.
     * After storing, updates the related content helper to refresh the cache.
     *
     * @param relatedContent the RelatedContent entity to store
     */
    public void store(final RelatedContent relatedContent) {

                                    <label for="doc.cache" class="col-sm-3 text-sm-right col-form-label">cache</label>
                                    <div class="col-sm-9">
                                        <la:errors property="doc.cache"/>
                                        <la:text styleId="doc.cache" property="doc.cache" styleClass="form-control"/>
                                    </div>

        assertFalse(fieldConfigs.getConfig("foo").map(FieldConfigs.Config::isOverwrite).orElse(false));
    }

    public void test_cache() {
        final Map<String, String> params = Maps.of("foo", "cache");
        FieldConfigs fieldConfigs = new FieldConfigs(params);
        assertTrue(fieldConfigs.getConfig("test").isEmpty());
        assertTrue(fieldConfigs.getConfig("foo").map(FieldConfigs.Config::isCache).orElse(false));

En un escenario avanzado donde sabes que necesitas que la dependencia se llame en cada paso (posiblemente varias veces) en el mismo request en lugar de usar el valor "cache", puedes establecer el parámetro `use_cache=False` al usar `Depends`:

import org.lastaflute.web.response.ActionResponse;
import org.lastaflute.web.response.HtmlResponse;
import org.lastaflute.web.util.LaRequestUtil;

import com.google.common.cache.Cache;
import com.google.common.cache.CacheBuilder;
import com.microsoft.aad.msal4j.AuthorizationCodeParameters;
import com.microsoft.aad.msal4j.ConfidentialClientApplication;
import com.microsoft.aad.msal4j.IAuthenticationResult;

Lokhttp3/internal/_UtilJvmKt;
Lokhttp3/internal/cache/CacheInterceptor$Companion;
Lokhttp3/internal/cache/CacheInterceptor$cacheWritingResponse$cacheWritingSource$1;
Lokhttp3/internal/cache/CacheInterceptor;
Lokhttp3/internal/cache/CacheRequest;
Lokhttp3/internal/cache/CacheStrategy;
Lokhttp3/internal/cache/DiskLruCache$Editor;
Lokhttp3/internal/cache/DiskLruCache$Entry;
Lokhttp3/internal/cache/DiskLruCache$Snapshot;

. {
  etcd churchofminio.com {
      endpoint http://localhost:2379 http://localhost:4001
      upstream /etc/resolv.conf
  }
  debug
  prometheus
  cache 160 mydomain.com
  loadbalance
  forward . /etc/resolv.conf

/**
 * A container for data that is specific to a session.
 * All components may use this storage to associate arbitrary data with a session.
 * <p>
 * Unlike a cache, this session data is not subject to purging. For this same reason, session data should also not be
 * abused as a cache (i.e. for storing values that can be re-calculated) to avoid memory exhaustion.
 * <p>
 * <strong>Note:</strong> Actual implementations must be thread-safe.
 *

 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.api.cache;

import org.apache.maven.api.annotations.Experimental;

/**
 * Enumeration defining different retention periods for cached data.
 * Each value represents a specific scope and lifetime for cached items.
 *
 * @since 4.0.0
 */
@Experimental
public enum CacheRetention {
    /**

## Version 4.1.1

_2019-09-05_

 *  Fix: Don't drop repeated headers when validating cached responses. In our Kotlin upgrade we
    introduced a regression where we iterated the number of unique header names rather than then
    number of unique headers. If you're using OkHttp's response cache this may impact you.


## Version 4.1.0

_2019-08-12_

 [brotli]: https://github.com/google/brotli