Naturally, you've got the "right" idea - and the elements are (almost) in place today. There's probably more legwork needed than a nicely wrapped framework would require, and there's a security concern that you need to cover yourself. What can be done today: - On the server side, you can use AppEngine to build a RESTful web server with a database back end. Authentication through Google Accounts. Bonus for using AppEngine: The user authentication is encrypted (SSL), right out of the box. - The aforementioned user authentication is integrated in the user facing part of the web server that you build. After logging on, it allows the user to check and manage his or her stored data - On the client side, use GET and POST methods to query the server (could be SOAP or something else, of course), based on the protocol that you implement. Most likely candidate is a XML-based protocol, I suppose. Where it's getting shaky as of today: The part where you access the implicit user authentication on the device. This is not covered by the Android SDK, and the solution currently is through a framework JAR that you download independent from the SDK. - At any rate, to comfort both users and dev, you do not gain or need access to user passwords, neither on the client, nor on the server side. - The downside as mentioned above, is the lacking formal integration of user account lookups in the SDK. As an added challenge, the user's gmail ID needs to directly travel along with every GET and POST call from the client side, or initially at least, if the protocol you implement has some form of session management. This is needed in order to allow the selection of the user's data in the backend database. The onus of encrypting the user's identifying information as part of your protocol is on you! JP
On Sep 19, 2:48 pm, Moto <[email protected]> wrote: > The idea is to allow developers to access a remote database provided > by google. In android the developer will need a special permission to > be set at the manifest file. This could allow applications to keep a > backup of users application data without having to sign in ever, > seamless. > > Users could than sign-in to their gmail and see a list of applications > that are currently storing data on their gmail space... The user > could be allowed to wipe the data or even block the application from > storing data to it... > > This idea make the most sense since Android will be a platform were > users will be constantly changing android phones as new better ones > come out... > > Well you get the idea... So what you think? GOOGLE you too....! :) > > -Moto! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
