HomeSort by relevance Sort by last modified time
    Searched refs:m_resourceToRevalidate (Results 1 - 2 of 2) sorted by null

  /external/webkit/Source/WebCore/loader/cache/
CachedResource.cpp 105 , m_resourceToRevalidate(0)
115 ASSERT(!m_resourceToRevalidate); // Should be true because canDelete() checks this.
394 ASSERT(!m_resourceToRevalidate);
403 // So the code needs to be robust to this assert failing thus the "if (m_resourceToRevalidate->m_proxyResource == this)" in CachedResource::clearResourceToRevalidate.
407 m_resourceToRevalidate = resource;
412 ASSERT(m_resourceToRevalidate);
414 if (m_resourceToRevalidate->m_proxyResource == this) {
415 m_resourceToRevalidate->m_proxyResource = 0;
416 m_resourceToRevalidate->deleteIfPossible();
419 m_resourceToRevalidate = 0
    [all...]
CachedResource.h 177 bool canDelete() const { return !hasClients() && !m_request && !m_preloadCount && !m_handleCount && !m_resourceToRevalidate && !m_proxyResource; }
203 bool isCacheValidator() const { return m_resourceToRevalidate; }
204 CachedResource* resourceToRevalidate() const { return m_resourceToRevalidate; }
287 // to to be clients of m_resourceToRevalidate and the resource is deleted. If not, the field is zeroed and this
289 CachedResource* m_resourceToRevalidate;
291 // If this field is non-null, the resource has a proxy for checking whether it is still up to date (see m_resourceToRevalidate).
294 // These handles will need to be updated to point to the m_resourceToRevalidate in case we get 304 response.

Completed in 20 milliseconds