For cases where you don't want to, or can't, 'fallback' on a cached resource.<div><br></div><div>ex 1.</div><div><br></div><div><a href="http://server/get/realtime/results/from/the/outside/world">http://server/get/realtime/results/from/the/outside/world</a><div>
Creating a fallback resource with a mock error or empty response is busy work.</div><div><br></div><div>ex 2.</div><div><br></div><div><a href="http://server/change/some/state/on/server/side?id=x&newValue=y">http://server/change/some/state/on/server/side?id=x&newValue=y</a></div>
<div>Ditto</div><div><br><div class="gmail_quote">On Wed, Sep 23, 2009 at 2:47 AM, Anne van Kesteren <span dir="ltr"><<a href="mailto:annevk@opera.com">annevk@opera.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
If you use a fallback namespace it will always try to do a network fetch before using the fallback entry so why is there a need for a NETWORK entry in the cache manifest?<br><font color="#888888">
<br>
<br>
-- <br>
Anne van Kesteren<br>
<a href="http://annevankesteren.nl/" target="_blank">http://annevankesteren.nl/</a><br>
</font></blockquote></div><br></div></div>