Thanks. So is there a better way to do this in Gears? Again, I'm running a changing slideshow with lots of images in it. The page won't refresh very often but will pull in new images periodically. Keeping them all in memory is probably a bad idea so I want to cache them on disk...but as that cache gets big I'll need to prune it, either based on the number of images in it or (even better) on the space it's consuming.
On Nov 7, 9:29 am, Austin <[EMAIL PROTECTED]> wrote: > Hi Dave, > > Unfortunately there is no support to store blobs into database, there is a > potential workaround as posted in this thread - > > http://groups.google.com/group/gears-users/browse_thread/thread/548b4... > > Hope that helps, > Austin > > On Fri, Nov 7, 2008 at 9:28 AM, Austin Chau <[EMAIL PROTECTED]> wrote: > > Hi Dave, > > > Unfortunately there is no support to store blobs into database, there is a > > potential workaround as posted in this thread - > > >http://groups.google.com/group/gears-users/browse_thread/thread/548b4... > > > Hope that helps, > > Austin > > > On Fri, Nov 7, 2008 at 7:32 AM, Dave <[EMAIL PROTECTED]> wrote: > > >> I'm writing an app that includes a slideshow of a fairly large number > >> of images, more than I want to trust to the browser's own caching > >> ability, so Gears seemed like a potential option. > > >> Because the usage model is to load a bunch of remote images and then > >> keep and manage them locally in the app, Database seemed more > >> appropriate than ResourceStore. Can you store JS Image objects (or > >> some serialized version of them) in Database? > > >> Thanks.
