dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
799
share rss forum feed


fukitol
Solon for President
Premium
join:2001-06-11
PonziWorld

need help re: HTML 5 local/session storage in Chrome

Right, so we're working on a Web-based application that's very heavy on JS, jQuery, all sorts of client-side tech. Nothing is installed on the user's machine, aside from Chrome. (Yes, we support only Chrome at this time, but it's a commercial application for a specific market.)

By far, the primary facility in the application involves loading and rendering HTML documents, as well as doing lots of client-side DOM manipulation. However, at least in the past, Chrome would totally lock up on a large document until it could load and render the entire thing. We're still assuming that that can happen, but we'd be ecstatic if this were no longer the case.

To work around this problem, we implemented caching of individual pages using HTML 5 session storage. That is, whenever the user opened a document in our application, the first x number of pages (separate HTML documents, really) would be fetched, rendered and session-stored. While the user was looking at that first set of pages, all subsequent pages would be fetched and session-stored within a background task of sorts, so that whenever the user went to a given page, the browser displayed it far more quickly than if we fetched it on demand from the server.

It used to be that Chrome allowed unlimited session storage. Very recently, however, Chrome implemented a session storage limit of 10MB per domain, which really only allows us to cache about 17 pages of one file, total.

Would anyone have thoughts on how to get around this jam? Does anyone have experience with IndexedDB or any other related things?
--
The truth is that the State is a conspiracy designed not only to exploit, but above all to corrupt its citizens. - Tolstoy


cdru
Go Colts
Premium,MVM
join:2003-05-14
Fort Wayne, IN
kudos:7
said by fukitol:

It used to be that Chrome allowed unlimited session storage. Very recently, however, Chrome implemented a session storage limit of 10MB per domain, which really only allows us to cache about 17 pages of one file, total.

Are you sure about that limit? According to Google's developer's guide it's unlimited up to available system resources. Perhaps your particular test bed doesn't have appropriate storage?