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

  /external/chromium_org/third_party/WebKit/Source/core/fetch/
Resource.cpp 126 , m_resourceToRevalidate(0)
145 ASSERT(!m_resourceToRevalidate); // Should be true because canDelete() checks this.
208 ASSERT(!m_resourceToRevalidate);
221 ASSERT(!m_resourceToRevalidate);
230 if (m_resourceToRevalidate)
252 ASSERT(!m_resourceToRevalidate);
327 if (!m_resourceToRevalidate)
341 ASSERT(!m_resourceToRevalidate);
588 ASSERT(!m_resourceToRevalidate);
597 // So the code needs to be robust to this assert failing thus the "if (m_resourceToRevalidate->m_proxyResource == this)" in Resource::clearResourceToRevalidate
    [all...]
Resource.h 203 bool canDelete() const { return !hasClients() && !m_loader && !m_preloadCount && !m_handleCount && !m_protectorCount && !m_resourceToRevalidate && !m_proxyResource; }
231 bool isCacheValidator() const { return m_resourceToRevalidate; }
232 Resource* resourceToRevalidate() const { return m_resourceToRevalidate; }
377 // to to be clients of m_resourceToRevalidate and the resource is deleted. If not, the field is zeroed and this
379 Resource* m_resourceToRevalidate;
381 // If this field is non-null, the resource has a proxy for checking whether it is still up to date (see m_resourceToRevalidate).
384 // These handles will need to be updated to point to the m_resourceToRevalidate in case we get 304 response.

Completed in 23 milliseconds