Using this, you can store all information that you need in one place, and a single query to IndexedDB can return all the data you need. This is specified by the IndexedDB spec and so far implemented in both the Firefox and IE implementations of IndexedDB. You can write a File or a Blob into IndexedDB just like you can store strings, numbers and JavaScript objects. IndexedDB treats file data just like any other type of data. Especially when there is a solution which can store both structured data as well as file data. However it seems a bit non-optimal to me to have to store some data separated from the rest. Today, people generally solve this by storing the images and sound files in a file system, and then store the file names of those files along with things like speed and firepower of the enemy. For example an enemy space ship might have a few associated images, as well as a couple of associated sounds, used when the enemy is moving around the screen and shooting. Games are a very common type of application where this is needed. This is useful if you need quick access to the resources, or if you want to be able to access them even if the user is offline. Probably the most common thing that people want to do is to simply store a set of resources so that they are available without having to use the network. In my opinion most, but so far not all, of these problems have better solutions than the FileSystem API. But note that this post represents my personal opinion, intended to spur more conversation on this topic.Īs stated above, people asking for “FileSystem API support” in Firefox are actually often interested in solving many different problems. This blog post is an attempt at giving my answer to this question and explain why we haven’t implemented the above two specifications. The specifications are quite big and feature full, so it’s no surprise that people are wanting to do very different things with it. The answer is somewhat complex, and depends greatly on what exact capabilities of the above two specifications the person is actually wanting to use. Usually, but not always, they are referring specifically to the FileSystem and FileWriter specifications which Google is implementing in Chrome, and which they have proposed for standardization in W3C. A question that I get asked a lot is why Firefox doesn’t support the FileSystem API.
0 kommentar(er)
