11.07.2015 Views

Client-Side Storage in Web Applications

Client-Side Storage in Web Applications

Client-Side Storage in Web Applications

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

5: var myData = {6: "code": "T-111.5502",7: "name": "Sem<strong>in</strong>ar on Media Technology B P"8: };9: ...10: // Create/open database11: myDatabase = openDatabase( "myItemDB", version,12: "My Item Database", 2 * 1024 * 1024 );13: ...14: // Start transaction15: myDatabase.transaction( function( dbTx ) {16: // Create table17: dbTx.executeSql( "CREATE TABLE IF NOT EXISTS18: myItems ( key TEXT UNIQUE, value TEXT )" );19: // Store data20: dbTx.executeSql( "INSERT INTO myItems VALUES21: ( '1', '" + JSON.str<strong>in</strong>gify( myData, null, "\t" )22: + "' )" );23: });24: ...25: // Start transaction26: myDatabase.transaction( function( dbTx ) {27: // Retrieve data28: dbTx.executeSql( "SELECT * FROM myItems29: WHERE key = '1'", [], function( exeTx, exeRS ) {30: var myResult =31: JSON.parse( exeRS.rows.item( 0 ).value );32: });33: });List<strong>in</strong>g 2. The <strong>Web</strong> SQL Database syntax example: first a database is created/opened, afterwhich data is stored and then retrieved.As of 18 th of November 2010, the specification work has stopped and the specificationis no longer <strong>in</strong> active ma<strong>in</strong>tenance. The reason beh<strong>in</strong>d this decision was that all<strong>in</strong>terested implementors have used the same SQL backend, i.e., SQLite, and thereforethe standardization process cannot proceed any further. Thus, the usage of the API isno longer recommended and developers are advised to use Indexed Database API [17]for the com<strong>in</strong>g web application development. In its current state, however, the APIprovides a viable option for stor<strong>in</strong>g data on mobile devices, as shown by Table 3 [21].7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!