This seems like something you might do in a servlet filter. Have you considered user specific namespaces if you completely want user data in silos? You can set the namespace in the servlet filter:
http://code.google.com/appengine/docs/java/multitenancy/multitenancy.html -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Wed, Jan 11, 2012 at 12:31 PM, meiaestro <[email protected]> wrote: > Thanks for the reply.**** > > ** ** > > You're right. I did not use the Users API, as I do not want to force the > users to have a google account (or any other existing account). This will > be optional at a later point in time.**** > > ** ** > > The user authentication happens on server side by a self-programmed > algorithm. Username and the hash values of the user's password are stored > in the datastore. So far this authentication is independent from any > session ID.**** > > > Hope this helps a bit. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine-java/-/_MQ2fHNOUqsJ. > > 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-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
