Home
last modified time | relevance | path

Searched refs:cacheUpdateFailed (Results 1 – 4 of 4) sorted by relevance

/external/webkit/Source/WebCore/loader/appcache/
DApplicationCacheGroup.cpp529 cacheUpdateFailed(); in didReceiveResponse()
625 cacheUpdateFailed(); in didFail()
640 cacheUpdateFailed(); in didFail()
667 cacheUpdateFailed(); in didReceiveManifestResponse()
686 cacheUpdateFailed(); in didFinishLoadingManifest()
710 cacheUpdateFailed(); in didFinishLoadingManifest()
772 void ApplicationCacheGroup::cacheUpdateFailed() in cacheUpdateFailed() function in WebCore::ApplicationCacheGroup
789 cacheUpdateFailed(); in cacheUpdateFailedDueToOriginQuota()
DApplicationCacheGroup.h128 void cacheUpdateFailed();
/external/webkit/Source/WebCore/
DChangeLog-2008-08-108062 There is no need to set any handles to 0 after calling cacheUpdateFailed(), since
8063 that is done inside the function. Furthermore, after calling cacheUpdateFailed() the cache
19709 Call cacheUpdateFailed.
19711 (WebCore::ApplicationCacheGroup::cacheUpdateFailed):
28293 (WebCore::ApplicationCacheGroup::cacheUpdateFailed):
DChangeLog-2009-06-1647078 (WebCore::ApplicationCacheGroup::cacheUpdateFailed):
52658 was call cacheUpdateFailed().
52664 (WebCore::ApplicationCacheGroup::didFinishLoadingManifest): Call cacheUpdateFailed()
80378 (WebCore::ApplicationCacheGroup::cacheUpdateFailed):