Using gdata with only one user in app engine, need to decide?

If this is a personal project, and you've only got a very small group of users, the design might be OK One really good reason to use OAuth is that you won't need to store the account password somewhere. Instead you'll be able to implement a simple 'setup' process to get and store an access token. OAuth is also nice since you'll be able to restrict the access scope However, I must say, I find your question very vague -- so more specific answers are difficult.

If this is a personal project, and you've only got a very small group of users, the design might be OK. One really good reason to use OAuth is that you won't need to store the account password somewhere. Instead you'll be able to implement a simple 'setup' process to get and store an access token.

OAuth is also nice since you'll be able to restrict the access scope. However, I must say, I find your question very vague -- so more specific answers are difficult.

Thanks for the answer. I realize there is no code in my question, but it's because what I needed was to make a decision over using my account@google. Com as the only owner of every document and then share with users, via access lists, or making users freely create and own documents with their own credentials.

Your answer is what I was looking for, btw. – misterte Aug 18 at 20:02.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.