Google IO - Part 1.1
After a brief lunch ( hit up the deli room and had a chicken sub ) and a trip back to my hotel room to drop off some stuff. I came back and immediately ran over to the google gears booth to absorb more info.
Out of all of the stuff here, Google Gears is the most interesting to me. Google Gears has so much potential, but i'm having problems coming up with practical applications in my field.
The only thing off the top of my head ( without any time to digest ) is to use gears to cache javascript and other relatively static content to speed up page loads. The cool thing about gears is - if you used it to cache items like that - then when the user accesses the information it shows up immedietly. But it also checks back to the server to see if it has changed and updates it in the local cache.
A few of the initial features of Google Gears:
- Cache and serve application resources (HTML, JavaScript, images, etc.) locally
- Store data locally in a fully-searchable relational database
- Make your web applications more responsive by performing resource-intensive operations asynchronously
http://code.google.com/apis/gears/samples/hello_world_managedstore/manag...
I'll update more later, need to absorb more data.