Hi George, What about using "get_current_user()"? Robert
On Fri, May 28, 2010 at 10:17 AM, George Moschovitis <[email protected]> wrote: > I was very pleased to see that the new OAuth API provides the same > interface as the Users API, but I see a missed opportunity here: > > If we had a unified API, ie: > > getCurrentUser() > > returned the user either through sign-in or OAuth we could use one > code path for both cases... > > Does this make sense? Is there a problem I am not seeing? > > -g. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" 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/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
