A URL with an MD5 digest in it will be incredibly ugly and not very
user-friendly. If you want your users to be able to actually remember
their URL to tell their friends, a user-chosen username as the id is
probably the best choice, even if it's not as easy on your end.
On Sep 8, 2:37 am, gops <[EMAIL PROTECTED]> wrote:
> Hi , In my application there is a user profile page.
>
> What is the best url scheme - numbering schme to refer to that user.
>
> some idea i have is ,
>
> user a incremental count of the user. {{ might need a global counter
> or a gql short query }} . and use it as an id.
> as done byhttp://www.challenge-you.com/profile?id=XX,
>
> Another id is to md5 user email and use it with .com/md5 ,
>
> or even faster , use key of datastore { but as I have multiple
> database model , this might be difficult }
>
> currently I am thinking to go with md5-idea. , but Is there easier
> way , I am not aware of ?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
