<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="http://tech.saigonist.com/taxonomy/term/117/all" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>cache</title>
    <link>http://tech.saigonist.com/taxonomy/term/117/all</link>
    <description></description>
    <language>en</language>
          <item>
    <title>Manage clearing / refreshing cache in Chrome when reloading page</title>
    <link>http://tech.saigonist.com/b/server/manage-clearing-refreshing-cache-chrome-when-reloading-page</link>
    <description>&lt;span class=&quot;submitted-by&quot;&gt;March 16, 2016&lt;/span&gt;&lt;div class=&quot;field_tags&quot;&gt;&lt;span class=&quot;label label-info&quot;&gt;&lt;a href=&quot;/tags/cache&quot;&gt;cache&lt;/a&gt;&lt;/span&gt; &lt;span class=&quot;label label-info&quot;&gt;&lt;a href=&quot;/tags/chrome&quot;&gt;chrome&lt;/a&gt;&lt;/span&gt; &lt;/div&gt;&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;p&gt;Web developers are constantly clicking the refresh button in their browser to see their latest changes. It almost becomes like a nervous tick, clicking that refresh to get that fix. And it&#039;s frustrating when changes on the backend don&#039;t result in the reward-inducing changes in the page loaded by the browser.&lt;/p&gt;

&lt;h2&gt;Web page caching explained&lt;/h2&gt;

&lt;p&gt;There&#039;s two levels of caching, and we deal with them in different places. First, there&#039;s flushing any cached resources in the browser, whether in the browser&#039;s memory or in files. And then there&#039;s requesting non-cached resources from the web...&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Wed, 16 Mar 2016 05:54:42 +0000</pubDate>
 <dc:creator>tomo</dc:creator>
 <guid isPermaLink="false">71 at http://tech.saigonist.com</guid>
  </item>
  </channel>
</rss>
