Thursday, February 15th, 2007
As Chris mentioned, there are four pieces to our offline puzzle… the only really new part is using &lquot;link rel=”offline-resource”&rquot; to put resources in a persistent “offline cache” that won’t accidentally evict your application. That is quite simple and once we’re confident we have the right semantics for it, we’ll definitely try to get it standardized somewhere.
One API that we are thinking about adding is support for script-controlled loading of resources into the offline cache. This needs to be designed in conjunction with a policy for deleting resources from the offline cache, something we haven’t settled on yet.
It’s a great update on the Mozilla team’s direction for off-line in future versions of Firefox.
Posted by Ben Galbraith at 7:00 am