INTRODUCTION TO HTML5
Well,the post is going to be entirely simple...covering only on the basic aspects of HTML5......
a)Offline Working-With " W3C HTML5 application cache" it is possible to make your web applications run offline as well as online.Now lemme explain you this feature in layman terms.
a)Web applications are becoming more complex and capable every day. There are many examples of web applications doing the same job as desktop applications in various fields (think about Google Docs, Picasa, etc.). However, one major disadvantage is that they cannot work when the user is not connected to the Internet.
This is where HTML5's new offline storage comes in. It tries to remove that disadvantage by defining a way to store files in a cache, so that when the user is offline, the browser still has access to the necessary files. These can be HTML, CSS or JavaScript files, or any other assets the site needs to run.
Just say for example,due to some reason you don't have e-access and you want to refer an important mail to reply to client.Then what...ohhh!!!!...simple html5 APPCACHE will allow you to store some of your mails so that you can refer them later.
This is possible due using APPCACHE manifest file.So the crux is "Like Google Gears it allows mechanism for ensuring Web applications are available even when the user is not connected to their network."
Hope that makes it pretty clear..:)
b)
Well,the post is going to be entirely simple...covering only on the basic aspects of HTML5......
a)Offline Working-With " W3C HTML5 application cache" it is possible to make your web applications run offline as well as online.Now lemme explain you this feature in layman terms.
a)Web applications are becoming more complex and capable every day. There are many examples of web applications doing the same job as desktop applications in various fields (think about Google Docs, Picasa, etc.). However, one major disadvantage is that they cannot work when the user is not connected to the Internet.
This is where HTML5's new offline storage comes in. It tries to remove that disadvantage by defining a way to store files in a cache, so that when the user is offline, the browser still has access to the necessary files. These can be HTML, CSS or JavaScript files, or any other assets the site needs to run.
Just say for example,due to some reason you don't have e-access and you want to refer an important mail to reply to client.Then what...ohhh!!!!...simple html5 APPCACHE will allow you to store some of your mails so that you can refer them later.
This is possible due using APPCACHE manifest file.So the crux is "Like Google Gears it allows mechanism for ensuring Web applications are available even when the user is not connected to their network."
Hope that makes it pretty clear..:)
b)
This is a very good article. Keep sharing... :)
ReplyDelete