would be called like. $.fn.cacheImages.drop('http://my.diamonds/are-awesome.jpg');
New param would prefix existing. Both would be optional and if both are undefined it should wipe everything with the default prefix. The check on the new URI param would check for a length greater then 1, and if that is true it would attempt to only drop that value. Would be helpful on the back-end cleaning up images when they are no longer needed.
This would allow for the caching of an image via it's remote URL without having to explicitly place it into the DOM. Could be very handy for html5 web apps that are attempting to make offline storage possible.
I'm sure I am not understanding something correctly but I am having a little trouble dropping a cached image and then causing it to be re-cached with an updated image. I am using the IndexedDB storage. I execute "$.fn.cacheImages.drop" to drop a specific image and then want to re-cache an updated image. The drop appears to be working ok according to the "Resources" tab in Chrome but the re-cache of the image seems to be finding an image already cached. What am I doing wrong? The following is my code:
localStorage has a fixed cap (currently) of about 5mb. This may change over time but for not we'll create an alternate storage method that would allow for more storage.