II'll check the docs. Thanks. If no caching is provided by default, you could write your app to download all the resources locally, then load a locally referenced html file. That is an awful lot of work, though. Definitely on the far side of reasonable. Certainly encourages one to return to the days of tiny html pages :)
On Tue, Aug 26, 2008 at 10:28 AM, Kevin Menard <[EMAIL PROTECTED]> wrote: > On Tue, Aug 26, 2008 at 9:49 AM, Ed Wrenbeck <[EMAIL PROTECTED]> wrote: > >> >> There are different caching options. It might be cached to disc, it >> might be cached only in memory, it might not be cached at all. It >> depends on what you do on the native side. I would just check the >> framework docs for what you want to do in that framework. For example, >> a framework might only allow in memory caching but not "on disc" >> caching. There can be other ways around the problem such as storing >> the html as a file on the local side and loading it as a string with a >> baseurl reference to the server. > > > I would love to be proven wrong on this, but I don't think there's any > reasonable way of providing your own caching mechanism. The problem is that > WebKit fetches all of the external resources on a page as a single > transaction when you load a request for a page. So, while you may be able > to load an HTML page saved to disk, you don't have the opportunity to hook > in to load all the other resources. > > -- > Kevin > > > > -- Rusty Zarse - VP Technology OckhamResearch.com / GlobalAccessHoldings.com 678-461-9793 / [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
