18. Silverlight IsolatedStorage http://www.shinedraw.com/data-handling/silverlight-vs-flash-local-storage/ using System.IO.IsolatedStorage.IsolatedStorageFile; IsolatedStorageFile store = IsolatedStorageFile.GetUserStoreForApplication(); if(store.FileExists(FILENAME)){ isfs = new IsolatedStorageFileStream(FILENAME, FileMode.OpenOrCreate, store); StreamReader streamReader = new StreamReader(isfs); string s; while ((s = streamReader.ReadLine()) != null) TextArea.Text += (s + ''); streamReader.Close(); } // save data to local storage IsolatedStorageFile store = IsolatedStorageFile.GetUserStoreForApplication(); IsolatedStorageFileStream isfs = new IsolatedStorageFileStream(FILENAME, FileMode.OpenOrCreate, store); StreamWriter streamWriter = new StreamWriter(isfs); streamWriter.Write("New Text"); streamWriter.Flush(); streamWriter.Close();
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
Hinweis der Redaktion
Historically, most desktop apps have this idea that when you open a document or database or any data-driven application, you have a certain amount of freedom to interact with that data without necessarily affecting the version that is saved on the disk. So if I change the font of my entire word doc to comic-sans just for fun to see what it looks like, I don’t need to worry about that change being permenant because I didn’t save it. Generally speaking, web apps don’t provide this ‘sandbox’ mode because it’s a major development effort to distinguish between data modifications that are sandboxed and ones that are permanent. And because the browser itself is for the most part not at all stateful or aware of the data you are working with – you have to provide that functionality on your own. Talk briefly about how you have used/needed persistent storage.
Byte limits.. Your cookies need to be encoded as well, as though you were embedding them in XML attributes which bumps up the size. Overloading your cookies has been known to crash browsers too.
The only thing not on this list is anything provided by Silverlight or possibly a Java Applet – but I know very little about these. Gears – no support for Safari 4 yet on snow leopard. Built right into chrome. Talk about window.name interesting features. How perf drops on FF around 2 mb. Data can be accessed off domain, etc. HTML5 Sqlite storage limits don’t appear to be enforced yet. Opera 3MB http://blog.futtta.be/2009/11/18/chrome-opera-to-support-html5-webdb-ff-ie-wont/ I should point out that Adobe AIR’s javascript interface is a bit of a different ball game. They have their own storage IO mechanisms, and support SQLite as well. ALSO: GOOGLE GEARS has been discontinued by google.
Can be read and written to outside its origin. Not crash safe, but extremely useful.
Can be read and written to outside its origin
Despite these negatives, sometimes there’s really no better way to do something
Despite these negatives, sometimes there’s really no better way to do something
Can be read and written to outside its origin
Can be read and written to outside its origin
Byte limits.. Your cookies need to be encoded as well, as though you were embedding them in XML attributes which bumps up the size. Overloading your cookies has been known to crash browsers too. In flash 9+ you can combine this with GZIP which is built right into the engine to really stretch this. With user permission you can increase this to massive amounts.
Web Hypertext Application Technology Working Group The WHATWG was founded by individuals from Apple , the Mozilla Foundation and Opera Software . [1] Since then, the editor of the WHATWG specifications, Ian Hickson , has moved to Google . Chris Wilson of Microsoft was invited but did not join, citing the lack of a patent policy to ensure all specifications can be implemented on a royalty-free basis Limited involvement from Microsoft. Not all vendors will implement all features.
http://blog.futtta.be/2009/11/18/chrome-opera-to-support-html5-webdb-ff-ie-wont/ - in order to have a webdb standard, you also have to specify (and standardize) the SQL-language to query that database, the question is what SQL-dialect to standardize on. - as the current implementations are all SQLite -based (including Google’s and Opera’s), the spec would have to describe the very specific SQL-dialect that SQLite uses (and maybe even of a specific version of SQLite) - http://blog.vlad1.com/2009/04/06/html5-web-storage-and-sql/ Enjoinment IE USED TO HAVE INLINE VIDEO AND AUDIO embedding: <img src=&quot;cover.gif&quot; dynsrc=&quot;clock.avi&quot; controls> http://sharovatov.wordpress.com/2009/06/05/html5-video-tag-and-internet-explorer/
There’s this other thing called globalStorage provided by FF which has been deprecated to my knowledge.
There’s this other thing called globalStorage provided by FF which has been deprecated to my knowledge.
DIFFERENCE IS: onstorage fires on both storage formats, but onstoragecommit only should fire on localstorage ALSO: onstoragecommit is ONLY for ie8 There’s this other thing called globalStorage provided by FF which has been deprecated to my knowledge. Can also use the JSON library here to support objects. For events: In FF and safari the event args are actually the storage event object. In IE you get an event object, and in safari you can an expanded object with additional properties. HTML5 origin (scheme + hostname + non-standard port)
http://developer.apple.com/safari/library/documentation/iPhone/Conceptual/SafariJSDatabaseGuide/UsingtheJavascriptDatabase/UsingtheJavascriptDatabase.html#//apple_ref/doc/uid/TP40007256-CH3-SW1 A database transaction comprises a unit of work performed within a database management system (or similar system) against a database, and treated in a coherent and reliable way independent of other transactions. Transactions in a database environment have two main purposes: To provide reliable units of work that allow correct recovery from failures and keep a database consistent even in cases of system failure, when execution stops (completely or partially) and many operations upon a database remain uncompleted, with unclear status. To provide isolation between programs accessing a database concurrently. Without isolation the programs' outcomes are typically erroneous.
http://blog.futtta.be/2009/11/18/chrome-opera-to-support-html5-webdb-ff-ie-wont/ - in order to have a webdb standard, you also have to specify (and standardize) the SQL-language to query that database, the question is what SQL-dialect to standardize on. - as the current implementations are all SQLite -based (including Google’s and Opera’s), the spec would have to describe the very specific SQL-dialect that SQLite uses (and maybe even of a specific version of SQLite) - http://blog.vlad1.com/2009/04/06/html5-web-storage-and-sql/ - enjoinment