+1. I didn't actually see those sessions so I'm not sure about the technical details, but I note that the new endpoints service is largely based on passing a User object around - I wonder whether that User object can also be used to represent a G++ user. Otherwise I wonder whether the endpoints folks will need to make some changes to respond to this new emphasis on G++ sign-in.
I disagree that G+ sign-in supersedes User sign in in every way. For one thing, they recently made it so that the act of installing an Android app with accounts permissions (e.g. accepting those permissions) is the same as granting the app access to your account - for the most basic level of authentication only. For apps that are not social, this is awesome - no need to prompt the user at all, and you can depend on having this. Tom On Friday, May 17, 2013 2:11:35 PM UTC-4, D X wrote: > > It seems like G+ SSO is a big deal at this year's I/O. > > I've been using the User service for authentication, and G+ SSO would > supercede the User service in every way. > Are there any plans to have the User service integrated with the G+ SSO > features described at I/O, or is this something we'll have to do on our own? > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
