Sorry guys, honestly I skip the first 2 chapter in that book because I have already read it before. So, because today I am learning the 3rd chapter, entitled HTML5 Storage API, I skip the review of the 1st 2 chapter. I hope in the future I can cover my experience in learning the basic of Mobile Web Application in Android and HTML5 + CSS3. So, wait for it.
I have already read a few pages in this chapter, and I can conclude that this article will mainly focus for using the database on the client-side more effectively. Yes, if you all have already developed a web before, when u intended to save information on database, u must use server-side script (like the most popular language in the world, PHP, Ruby, Phyton, etc). But, HTML5 provided a different approach by including Storage API in their specification. In other words, u must not always connect to the server to use a database, implicate that the bandwidth can be reserved more efficient. From mobile architecture perspective, this approach can benefit “thin client” architecture more than “smart client” architecture, because thin client have yet used the local storage, while “smart client” have already used a local storage before (like SQLite).
Essentially, there are three different types of client-side storage mechanisms are being implemented as part of the HTML5 specification:
- Web Storage (key/value pairs)
- Web SQL Database (SQLite-like database)
- Indexed Database (intended to replace Web SQL Database, objects-based