Hi,
1) You are right: storing in ds is required in your case
2) You could use the Google Login service: very secured and will take
care of login persistence for you
See http://code.google.com/appengine/docs/java/users/
3) Channel API is done to meet you needs (even at very high rate of
polling):
Hi Didier, thanks for your reply.
I forgot to mention that my game client is a stand-alone application
(desktop & mobile), not a regular web page, so I'm quite restricted in
term of "web" capabilities on the client side. Right now, all I can do
is GET & POST http requests, and possibly provide add
Hi Spk,
[to access the datastore, I recommend you to use Objectify - my
personal choice - developped by Jeff Schnitzer that answered above -
JDO/JPA investment by Google is now less and they push packages like
Objectify and other alternatives]
About your complements
1) The google login service i
A couple words of advice:
Nearly any third-party authentication system will require that you
perform the login process in a web browser, but you should still use
one even for desktop apps. Systems that ask you to create a login are
almost anachronistic these days. Use google login, or facebook l
