Linked by David Adams on Sat 6th Sep 2008 14:34 UTC
Thread beginning with comment 329491
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
It's not quite that simple. Take, for example, Google Mail. Yes, the emails are stored on a google server, but with gears, a copy can also be kept on the client machine, allowing offline access, Similarly, the whole Gmail 'application' can be automatically stored locally to allow offline use. This sort of thing makes synchronisation really easy, in a manner that is transparent to the user.
It's not quite that simple. Take, for example, Google Mail. Yes, the emails are stored on a google server, but with gears, a copy can also be kept on the client machine, allowing offline access, Similarly, the whole Gmail 'application' can be automatically stored locally to allow offline use. This sort of thing makes synchronisation really easy, in a manner that is transparent to the user.
So what's the difference between that an IMAP? Or even spoofing Pop3 as IMAP (e.g. not allowing the client to delete messages)?
Really, nothing is gained by it for e-mail.
On the other hand, Google Gears really helps Google with its Productivity Suite (e.g. Docs, Spreadsheet) since they can then be run in off-line mode. But it's not a big help for Gmail...




Member since:
2005-11-15
Cloudy thinking makes for nice fluffy little diagrams that an IT executive can understand. Sometimes things get so high level they become meaningless. Chrome is just a browser; google mail just stores my mail on some servers, there is no magic involved and drawing a cloud adds nothing useful to a conservation.
You can tell browsers are defective every day when you use them so they certainly need fixing.