I have thought about this and will probably do so. I was just hoping it would be easy to just add an additional namespace. Seems cleaner to me.
On May 20, 11:46 am, Andy Mikhailenko <neith...@gmail.com> wrote: > What about using emails or openIDs for authentication? These include > namespaces per se ;) > > On May 20, 1:09 am, Timboy <corn13r...@gmail.com> wrote: > > > Initially we will have in the ballpark of 10,000 Private users. Anyone > > have an idea on an additional user namespace? > > > On May 19, 8:42 am, Aneesh <aneeshvkulka...@gmail.com> wrote: > > > > How many private users do you have? If it's just a small number, > > > consider using the same model for all Users, and making some profiles > > > public/private. A couple usernames will be taken, but that shouldn't > > > be a big deal. > > > > If you actually want a second namespace, I'm not sure of the best way > > > to proceed. > > > > On May 18, 9:28 pm, Timboy <corn13r...@gmail.com> wrote: > > > > > I have a normal User model for our private users of our project we > > > > also have a UserProfile for those users. > > > > > We need to have a public portion of our site as well with a separate > > > > user namespace. > > > > > Please advise the best way to achieve our goal. > > > > > TIA --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
