Provide skeleton functionality for AppCache handling in the network service.
We have a new class AppCacheNetworkServiceHandler which gets created on the IO thread. This class provides functionality for checking if a request can be serviced out of the AppCache. I was looking at AppCacheRequestHandler for this as well. However that class is tied deeply to the underlying job which gets a touch complicated for lifetime managemnt if the request is not really being served out the cache. Added some comments for that class to see if we could remove it once the pieces begin to align. This class implements the AppCacheStorage::Delegate interface which tells us if a response is available for a URL. Currently we just trace if a response is found and call the StartURLRequest callback in both cases. Going forward the plan is to create a URLLoaderFactory for AppCache and pass it back to the callback. Optionally we could create the loader right there as well. Thanks to jam for pointing that out. The other changes are to have the original ResourceRequest pointer in the AppCacheURLLoaderRequest class instead of a copy. We ensure that ownership is transferred correctly. BUG=715632 Review-Url: https://codereview.chromium.org/2874663004 Cr-Commit-Position: refs/heads/master@{#471120}
Showing
Please register or sign in to comment