On 11/09/2006, at 9:16 AM, Tamara D. Snyder wrote:
>
> Hi All,
>
> There is a web application I would like to write for a class I teach
> at the university. I would like my students to be able to log in and
> do something ("homework" if you like).
>
> I'd like to reuse the application next semester, with a different set
> of students. And I naturally don't want my students to have any
> access at all to the admin site.
thats cool.. you can write a script to wipe your student database
afterwards,
or just mark them as inactive in the auth system.
you can also 'hide' the admin section on another machine if you feel
that your students
are particularly prone to 'hacking'.
regardless of which auth system you use, you will need to have some
sort of method of 'starting anew'
when the next semester starts I'm guessing.
>
> I have considered making the database that contains all the student
> data - names, scores, etc. - one of the backends for the auth
> system. But now I am wondering if that is really what I want to do.
> Maybe I don't really want to log them in at all. Maybe I should
> create my own authentication system, and just recored if they are
> "OK" or not in the session, basically as just another cookie.
you could do that, but having the information only stored in a cookie
would mean
they would lose it if they switched to another browser, or used
another computer.
one another project I worked on, we used a separate user table to
authenticate against.
what that meant was all the existing functionality of django's auth
system needed to be
re-implemented. .. a big waste of time, and resources.
speaking from personal experience... use the standard auth app, and
possibly use some add on's
like http://svn.zyons.python-hosting.com/trunk/zilbo/common/
accounts/ to help manage the students
lost passwords etc.
regards
Ian
> That
> means that they would technically anonymous users, but with with a
> status that allows them to access certain "homework" pages. Then I
> would not have to worry that 330 people may potentially be allowed
> into the admin site at all.
>
> Many of you have lots more experience at this sort of thing than I
> do. What do you think? Should I use the django provided auth system
> with my student database as a backend, or should I create my own
> thing?
>
> Thanks for your opinions!
>
> Tamara
>
>
>
> >
--
Ian Holsman
[EMAIL PROTECTED]
join http://gypsyjobs.com the marketplace for django developers
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
