I'm doing research to see if Gears is something I can use for my situation. What I have is a web-based intranet email system, written using Java, that makes calls back to the server to read/send emails, etc. I want to be able to have my clients read their emails from their laptops inside our network and save static pages of the inbox at its current state and the messages that they read so they can access them from their laptops outside the network. Everything I was looking at in the examples dealt with only static html pages, but our pages are dynamically generated with .do extensions. Does Gears just save the generated .do as an html file?
My next question is how involved do the clients have to be in making the content go offline? Many of them are not very good with computers and I want it to be as easy for them as possible. I did see that they would be asked to allow Gears to run the first time they hit it, but after that it would run automatically. I believe that will be OK, but want to make sure that is all they will have to do. Last, I want to make sure this will work well with IE 6+. This is the only browser they will have access too and I want to make sure everything works smoothly (as many things don't in IE without a little tweaking). Thanks in advance for your help!
