Index: mojo/services/url_response_disk_cache/public/interfaces/url_response_disk_cache.mojom |
diff --git a/mojo/services/url_response_disk_cache/public/interfaces/url_response_disk_cache.mojom b/mojo/services/url_response_disk_cache/public/interfaces/url_response_disk_cache.mojom |
deleted file mode 100644 |
index abeb62f7d30b73bb56995e8e7db730449ac81e63..0000000000000000000000000000000000000000 |
--- a/mojo/services/url_response_disk_cache/public/interfaces/url_response_disk_cache.mojom |
+++ /dev/null |
@@ -1,60 +0,0 @@ |
-// Copyright 2015 The Chromium Authors. All rights reserved. |
-// Use of this source code is governed by a BSD-style license that can be |
-// found in the LICENSE file. |
- |
-[DartPackage="mojo_services"] |
-module mojo; |
- |
-import "mojo/public/interfaces/network/url_response.mojom"; |
- |
-// This service allows client to efficiently cache and retrieve url response |
-// content on disk. In particular, it allows the shell and content handlers to |
-// efficiently cache and retrieve mojo applications. |
-// TODO(qsr): At the moment, the url response disk cache only handles ETag. If |
-// either the cached version or the given response do not contain |
-// ETags, the entry will be invalidated. It should be extended to |
-// handle all the other http cache mechanisms for better performance |
-// with http servers that do not support ETags. |
-interface URLResponseDiskCache { |
- |
- // Given an URL, returns a tuple. If the |url| is not in the cache, all the |
- // response parameters are null. Otherwise |response| is the cached response |
- // stripped of the body, |file_path| is a file containing the body of the |
- // response and |cache_dir_path| is a directory that the applicaton can use |
- // to store content. This service guarantee that |cache_dir_path| will be |
- // emptied when |file_path| content changes. For example, a content handler |
- // that is backed by a VM that compiles files could have the VM use this |
- // directory to cache the compiled files. After |Get| has been called and a |
- // response is returned, the caller must call |Validate| or |Update| to |
- // revalidate the entry. If this is not done, a future call to |Get| may |
- // return null. |
- Get(string url) => (mojo.URLResponse? response, |
- array<uint8>? file_path, |
- array<uint8>? cache_dir_path); |
- |
- // Validate the cache for the given |url|. This will enforce that |Get| will |
- // return an entry if it exists. |
- Validate(string url); |
- |
- // Update the cache with the given response. |
- Update(mojo.URLResponse response); |
- |
- // Given a URLResponse, updates the cache and returns a pair of paths. |
- // |file_path| is a file containing the body of the response. |
- // |cache_dir_path| is a directory that the applicaton can use to store |
- // content. This service guarantee that |cache_dir_path| will be emptied |
- // when |file_path| content changes. For example, a content handler that is |
- // backed by a VM that compiles files could have the VM use this directory |
- // to cache the compiled files. |
- UpdateAndGet(mojo.URLResponse response) => |
- (array<uint8>? file_path, array<uint8>? cache_dir_path); |
- |
- // Given a URLResponse that is expected to have a zipped body, updates the |
- // cache and returns a pair of paths. |extracted_dir_path| is a directory |
- // containing the unzipped body of the response. |cache_dir_path| is a |
- // directory that the applicaton can use to store content. This service |
- // guarantee that |cache_dir_path| will be emptied when |extracted_dir_path| |
- // content changes. |
- UpdateAndGetExtracted(mojo.URLResponse response) => |
- (array<uint8>? extracted_dir_path, array<uint8>? cache_dir_path); |
-}; |